Re: [us...@httpd] 503 status seems to get cached - how do I disable caching?
Glad to have ben of some help, and thanks for sharing your results. It's always fun to deal with an interesting issue and cooperating poster. As a matter of fact, the result of your investigation will be quite helpful for me too. Although I'm using mod_jk and not mod_proxy, I'm quite sure that there must be some equivalent parameter in mod_jk. I'll have a look for it. Jenny Brown wrote: You got me going in a good general direction -- the real solution is slightly different. Here's what I found. In the parameters section of the ProxyPass directive, there is a parameter called retry. It defaults to 60 seconds. The description is such: "Connection pool worker retry timeout in seconds. If the connection pool worker to the backend server is in the error state, Apache will not forward any requests to that server until the timeout expires. This enables to shut down the backend server for maintenance, and bring it back online later. A value of 0 means always retry workers in an error state with no timeout." I changed it to 0 on my dev server, retested, and it works beautifully. Once I bring Tomcat back up, Apache recovers right away. This is the behavior I wanted. Thanks for the help! Problem solved. Jenny Brown On Wed, Jun 10, 2009 at 2:31 PM, André Warnier wrote: Jenny Brown wrote: On Wed, Jun 10, 2009 at 3:06 AM, André Warnier wrote: So, to get back to the original issue : if indeed the observed behaviour derives from such a timeout on the part of mod_proxy, I would suggest to do some thinking about whether it is not better, in a general sense, to leave things as they are, at least if this is a system destined to be deployed in production. After all, I am sure that if the developers of mod_proxy and/or mod_prox_ajp deemed it justified to introduce such a timeout, they probably thought hard about it and decided that it was A Good Thing. Oh, I'm okay with some delay. But I'd prefer a delay along the lines of 5-10 seconds, not close to a full minute. What I'm looking for is a way to control the length of the delay, or really any aspect of its behavior at all. Is there a configuration option for that? How would I go about finding out / where should I look? here ? http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxytimeout - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
[us...@httpd] segfault while migrating from RHEL4 to centOS 4.2 on apache 2.2.4 as proxy
Hi, I need some help in migrating our existing code from RHEL4 to centOS 4.2. We use apache configured as a proxy server and ,we have an out filter module registered with apache 2.2.4, where we gets the page content and do some processing based on the content. Everything worked fine in RHEL4 but when the same code was migrated to CentOS4.2 and compiled there ,a segmentation fault occurs while loading the module. we have some infilter modules also registered but did not face any problem with loading them, the issue is with the loading the out filter. details of the setup apache was configured with following command ./configure --prefix=/usr/local/apache2 --enable-mods-shared="proxy_connect proxy_ftp proxy_http proxy status rewrite deflate" --with-mpm=worker --with-included-apr uname -a : Linux srv-ind-ffi12.vanenburg.com 2.6.9-22.ELsmp #1 SMP Sat Oct 8 19:11:43 CDT 2005 i686 i686 i386 GNU/Linux gcc version: Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-java-awt=gtk --host=i386-redhat-linux Thread model: posix gcc version 3.4.4 20050721 (Red Hat 3.4.4-2) The following is the back trace using gdb. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208027456 (LWP 16497)] 0x009d9641 in __gnu_cxx::__exchange_and_add () from /usr/lib/libstdc++.so.6 (gdb) bt #0 0x009d9641 in __gnu_cxx::__exchange_and_add () from /usr/lib/libstdc++.so.6 #1 0x00ee4fc5 in __tcf_4 () from /usr/local/apache2/modules/mod_np_dynamic_filter.so #2 0x0013b6e4 in __cxa_finalize () from /lib/tls/libc.so.6 #3 0x00eaacea in __do_global_dtors_aux () from /usr/local/apache2/modules/mod_np_dynamic_filter.so #4 0x00f184de in _fini () from /usr/local/apache2/modules/mod_np_dynamic_filter.so #5 0x0020df6b in _dl_close () from /lib/tls/libc.so.6 #6 0x00418d5a in dlclose_doit () from /lib/libdl.so.2 #7 0x00a9d07e in _dl_catch_error () from /lib/ld-linux.so.2 #8 0x004192bb in _dlerror_run () from /lib/libdl.so.2 #9 0x00418d8a in dlclose () from /lib/libdl.so.2 #10 0x00b260b5 in dso_cleanup (thedso=0x9ba8ed0) at dso/unix/dso.c:72 #11 0x00b2b2d1 in run_cleanups (cref=0x9b240b8) at memory/unix/apr_pools.c:2034 #12 0x00b2c04d in apr_pool_clear (pool=0x9b240a8) at memory/unix/apr_pools.c:689 #13 0x08062024 in main (argc=3, argv=0xbff26764) at main.c:667 (gdb) q Did some one face the same problem ,or can anyone give me an idea regarding the problem/solution. Thanks & regards, Manohar. The information contained in this communication is confidential, intended solely for the use of the individual or entity to whom it is addressed and may be legally privileged and protected by professional secrecy. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. This email does not constitute any commitment from Cordys Holding BV or any of its subsidiaries except when expressly agreed in a written agreement between the intended recipient and Cordys Holding BV or its subsidiaries. Cordys is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt. Cordys does not guarantee that the integrity of this communication has been maintained nor that the communication is free of viruses, interceptions or interference. If you are not the intended recipient of this communication please return the communication to the sender and delete and destroy all copies. - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
[us...@httpd] Apache with multiple instance of jboss on same server
Hi, We have Apache Web server which is to be linked to 2 jboss instances on the same server. We have made the entries in workers.properties file but what changes need to be done in Jboss so that both instances are picked up by Apache load balancer? I tried changing Connector port="8009" to 8007 for the second instance but it doesnt seem to work. Can anyone please help me out with this? Regards, Nilesh -- View this message in context: http://www.nabble.com/Apache-with-multiple-instance-of-jboss-on-same-server-tp23979597p23979597.html Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com. - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [us...@httpd] segfault while migrating from RHEL4 to centOS 4.2 on apache 2.2.4 as proxy
On Thu, 2009-06-11 at 16:12 +0530, gmanohar wrote: > Hi, > > I need some help in migrating our existing code from RHEL4 to centOS 4.2. > We use apache configured as a proxy server and ,we have an out filter > module registered with apache 2.2.4, where we gets the page content and > do some processing based on the content. > Everything worked fine in RHEL4 but when the same code was migrated to > CentOS4.2 and compiled there ,a segmentation fault occurs while loading > the module. > we have some infilter modules also registered but did not face any > problem with loading them, the issue is with the loading the out filter. > > details of the setup > apache was configured with following command > > ./configure --prefix=/usr/local/apache2 > --enable-mods-shared="proxy_connect proxy_ftp proxy_http proxy status > rewrite deflate" --with-mpm=worker --with-included-apr > > uname -a : > Linux srv-ind-ffi12.vanenburg.com 2.6.9-22.ELsmp #1 SMP Sat Oct 8 > 19:11:43 CDT 2005 i686 i686 i386 GNU/Linux > > gcc version: > > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --disable-libunwind-exceptions --enable-java-awt=gtk > --host=i386-redhat-linux > Thread model: posix > gcc version 3.4.4 20050721 (Red Hat 3.4.4-2) ^^^ Thought it was recompiled on the CentOS box? > > The following is the back trace using gdb. > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread -1208027456 (LWP 16497)] > 0x009d9641 in __gnu_cxx::__exchange_and_add () from /usr/lib/libstdc++.so.6 > (gdb) bt > #0 0x009d9641 in __gnu_cxx::__exchange_and_add () from > /usr/lib/libstdc++.so.6 > #1 0x00ee4fc5 in __tcf_4 () from > /usr/local/apache2/modules/mod_np_dynamic_filter.so > #2 0x0013b6e4 in __cxa_finalize () from /lib/tls/libc.so.6 > #3 0x00eaacea in __do_global_dtors_aux () from > /usr/local/apache2/modules/mod_np_dynamic_filter.so > #4 0x00f184de in _fini () from > /usr/local/apache2/modules/mod_np_dynamic_filter.so > #5 0x0020df6b in _dl_close () from /lib/tls/libc.so.6 > #6 0x00418d5a in dlclose_doit () from /lib/libdl.so.2 > #7 0x00a9d07e in _dl_catch_error () from /lib/ld-linux.so.2 > #8 0x004192bb in _dlerror_run () from /lib/libdl.so.2 > #9 0x00418d8a in dlclose () from /lib/libdl.so.2 > #10 0x00b260b5 in dso_cleanup (thedso=0x9ba8ed0) at dso/unix/dso.c:72 > #11 0x00b2b2d1 in run_cleanups (cref=0x9b240b8) at > memory/unix/apr_pools.c:2034 > #12 0x00b2c04d in apr_pool_clear (pool=0x9b240a8) at > memory/unix/apr_pools.c:689 > #13 0x08062024 in main (argc=3, argv=0xbff26764) at main.c:667 > (gdb) q > > Did some one face the same problem ,or can anyone give me an idea > regarding the problem/solution. > > Thanks & regards, > Manohar. So it dies when unloading the (custom module) mod_np_dynamic_filter.so, when calling __cxa_finalize(), which is a libc function called to handle destructing all global and static local C++ objects, and to call all registered C++ atexit() handlers. I think that either the module was compiled with a different compiler than httpd, or that your module tries to shutdown a library that has changed version in the move. Either way, this has nothing to do with apache, it is all in your proprietary code. Cheers Tom - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [us...@httpd] Apache with multiple instance of jboss on same server
On Thu, 2009-06-11 at 04:34 -0700, nilesh p wrote: > Hi, > > We have Apache Web server which is to be linked to 2 jboss instances on the > same server. > We have made the entries in workers.properties file but what changes need to > be done in Jboss so that both instances are picked up by Apache load > balancer? > I tried changing Connector port="8009" to 8007 for the second instance but > it doesnt seem to work. > > Can anyone please help me out with this? > > Regards, > Nilesh Can you provide any of your configuration? I'd absolutely love to guess, but I left my magic guessing hat at home. Cheers Tom - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
[us...@httpd] Re: Apache with multiple instance of jboss on same server
:) Its like this, My workers.properties file is as below worker.list=loadbalancer worker.loadbalancer.type=lb #worker.loadbalancer.balance_workers=server1,server2,server3 worker.loadbalancer.balance_workers=server2,server3,server4,server5 worker.loadbalancer.sticky_session=true # Set properties for worker 'server1' (ajp13) #worker.server1.type=ajp13 #worker.server1.host=IP1 #worker.server1.port=8009 #worker.server1.cachesize=10 #worker.server1.cache_timeout=600 #worker.server1.socket_keepalive=1 #worker.server1.reclycle_timeout=300 # Set properties for worker 'server2' (ajp13) worker.server2.type=ajp13 worker.server2.host=IP2 worker.server2.port=8009 worker.server2.cachesize=10 worker.server2.cache_timeout=600 worker.server2.socket_keepalive=1 worker.server2.reclycle_timeout=300 # Set properties for worker 'server3' (ajp13) worker.server3.type=ajp13 worker.server3.host=IP3 worker.server3.port=8009 worker.server3.cachesize=10 worker.server3.cache_timeout=600 worker.server3.socket_keepalive=1 worker.server3.reclycle_timeout=300 # Set properties for worker 'server4' (ajp13) worker.server4.type=ajp13 worker.server4.host=IP4 worker.server4.port=8009 worker.server4.cachesize=10 worker.server4.cache_timeout=600 worker.server4.socket_keepalive=1 worker.server4.reclycle_timeout=300 # Set properties for worker 'server5' (ajp13) worker.server5.type=ajp13 worker.server5.host=IP4 worker.server5.port=8009 worker.server5.cachesize=10 worker.server5.cache_timeout=600 worker.server5.socket_keepalive=1 worker.server5.reclycle_timeout=300 As you can see, Server4 and Server5 have the same IP (IP4) and both are jboss instances. On the IP4 server(linux box), i have copied two exactly same instances of Jboss. In the server.xml file of 1st jboss instance all configurations are default config (8080) whereas in the server.xml of 2nd jboss instance, i have changed port to 9080.Thats it. now when i start only 1st Jboss instance, it works pretty fine but when i start the 2nd instance, the application starts to crash. I have given XMX=XMS=1024m for both the instances and the server has 4 gb of physical memory. I can view the WEB-CONSOLE of 1st jboss instance and find 10 connections. I am not very clear if apache is actually using the 2nd instance and why does the application crash the error that i get is "Your Application session has expired or an unexpected error has occured!!!" Can anyone help me out ? :( -- View this message in context: http://www.nabble.com/Apache-with-multiple-instance-of-jboss-on-same-server-tp23979597p23981040.html Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com. - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [us...@httpd] Re: Apache with multiple instance of jboss on same server
Hi. The configuration you provide below does not seem to make much sense. Why do you have 2 workers (4 and 5), connecting to the /same/ back-end (IP4) on the same port (8009) ? No wonder something is getting confused. I have not cross-checked the rest, but generally speaking : 1 "worker", port X at Apache level <--> 1 at the Tomcat/JBoss level. The HTTP connectors at the Tomcat/JBoss level have no role in this, only the AJP . And each instance must have different ports. nilesh p wrote: :) Its like this, My workers.properties file is as below worker.list=loadbalancer worker.loadbalancer.type=lb #worker.loadbalancer.balance_workers=server1,server2,server3 worker.loadbalancer.balance_workers=server2,server3,server4,server5 worker.loadbalancer.sticky_session=true # Set properties for worker 'server1' (ajp13) #worker.server1.type=ajp13 #worker.server1.host=IP1 #worker.server1.port=8009 #worker.server1.cachesize=10 #worker.server1.cache_timeout=600 #worker.server1.socket_keepalive=1 #worker.server1.reclycle_timeout=300 # Set properties for worker 'server2' (ajp13) worker.server2.type=ajp13 worker.server2.host=IP2 worker.server2.port=8009 worker.server2.cachesize=10 worker.server2.cache_timeout=600 worker.server2.socket_keepalive=1 worker.server2.reclycle_timeout=300 # Set properties for worker 'server3' (ajp13) worker.server3.type=ajp13 worker.server3.host=IP3 worker.server3.port=8009 worker.server3.cachesize=10 worker.server3.cache_timeout=600 worker.server3.socket_keepalive=1 worker.server3.reclycle_timeout=300 # Set properties for worker 'server4' (ajp13) worker.server4.type=ajp13 worker.server4.host=IP4 worker.server4.port=8009 worker.server4.cachesize=10 worker.server4.cache_timeout=600 worker.server4.socket_keepalive=1 worker.server4.reclycle_timeout=300 # Set properties for worker 'server5' (ajp13) worker.server5.type=ajp13 worker.server5.host=IP4 worker.server5.port=8009 worker.server5.cachesize=10 worker.server5.cache_timeout=600 worker.server5.socket_keepalive=1 worker.server5.reclycle_timeout=300 As you can see, Server4 and Server5 have the same IP (IP4) and both are jboss instances. On the IP4 server(linux box), i have copied two exactly same instances of Jboss. In the server.xml file of 1st jboss instance all configurations are default config (8080) whereas in the server.xml of 2nd jboss instance, i have changed port to 9080.Thats it. now when i start only 1st Jboss instance, it works pretty fine but when i start the 2nd instance, the application starts to crash. I have given XMX=XMS=1024m for both the instances and the server has 4 gb of physical memory. I can view the WEB-CONSOLE of 1st jboss instance and find 10 connections. I am not very clear if apache is actually using the 2nd instance and why does the application crash the error that i get is "Your Application session has expired or an unexpected error has occured!!!" Can anyone help me out ? :( - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [us...@httpd] Re: Apache with multiple instance of jboss on same server
On Thu, 2009-06-11 at 06:12 -0700, nilesh p wrote: > :) > Its like this, > > My workers.properties file is as below > > worker.list=loadbalancer > > > worker.loadbalancer.type=lb > #worker.loadbalancer.balance_workers=server1,server2,server3 > worker.loadbalancer.balance_workers=server2,server3,server4,server5 > worker.loadbalancer.sticky_session=true > > # Set properties for worker 'server1' (ajp13) > #worker.server1.type=ajp13 > #worker.server1.host=IP1 > #worker.server1.port=8009 > > #worker.server1.cachesize=10 > #worker.server1.cache_timeout=600 > #worker.server1.socket_keepalive=1 > #worker.server1.reclycle_timeout=300 > > # Set properties for worker 'server2' (ajp13) > worker.server2.type=ajp13 > worker.server2.host=IP2 > worker.server2.port=8009 > > worker.server2.cachesize=10 > worker.server2.cache_timeout=600 > worker.server2.socket_keepalive=1 > worker.server2.reclycle_timeout=300 > > # Set properties for worker 'server3' (ajp13) > worker.server3.type=ajp13 > worker.server3.host=IP3 > worker.server3.port=8009 > > worker.server3.cachesize=10 > worker.server3.cache_timeout=600 > worker.server3.socket_keepalive=1 > worker.server3.reclycle_timeout=300 > > # Set properties for worker 'server4' (ajp13) > worker.server4.type=ajp13 > worker.server4.host=IP4 > worker.server4.port=8009 > > worker.server4.cachesize=10 > worker.server4.cache_timeout=600 > worker.server4.socket_keepalive=1 > worker.server4.reclycle_timeout=300 > > # Set properties for worker 'server5' (ajp13) > worker.server5.type=ajp13 > worker.server5.host=IP4 > worker.server5.port=8009 > > worker.server5.cachesize=10 > worker.server5.cache_timeout=600 > worker.server5.socket_keepalive=1 > worker.server5.reclycle_timeout=300 > > > As you can see, Server4 and Server5 have the same IP (IP4) and both are > jboss instances. > On the IP4 server(linux box), i have copied two exactly same instances of > Jboss. > In the server.xml file of 1st jboss instance all configurations are default > config (8080) > whereas in the server.xml of 2nd jboss instance, i have changed port to > 9080.Thats it. > now when i start only 1st Jboss instance, it works pretty fine but when i > start the 2nd instance, the application starts to crash. I have given > XMX=XMS=1024m for both the instances and the server has 4 gb of physical > memory. > > I can view the WEB-CONSOLE of 1st jboss instance and find 10 connections. > I am not very clear if apache is actually using the 2nd instance and why > does the application crash > the error that i get is "Your Application session has expired or an > unexpected error has occured!!!" > > Can anyone help me out ? :( > I thought you were asking about apache httpd server configuration? Those all look like JBoss configuration - JBoss configuration/application crashes are best debugged on the JBoss lists btw. Please provide your apache configuration, or at least some indication of what it is. Cheers Tom - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [us...@httpd] Apache with multiple instance of jboss on same server
Nilesh, The two JBoss instances need to be on different ports in case they are running on the same physical server with one IP address. Your workers.properties file has a discrepancy regarding the server4 and server5 workers. Before working on Apache tomcat connector configuration, try running the two Jboss server instances simultaneously on the same server. If you succeed in that, the Apache+tomcat+mod_jk configuration is straight forward. Let me know if you need help regarding Jboss configurations. This list does not allow discussions about Jboss configuration. Send a seperate email regarding JBoss to me/JBoss discussion groups. Once you are able to run multiple Jboss instances, then we can come back to this list with details regarding JBoss+apache connection using mod_jk. Regards, Sushant On Thu, Jun 11, 2009 at 5:04 PM, nilesh p wrote: > > Hi, > > We have Apache Web server which is to be linked to 2 jboss instances on the > same server. > We have made the entries in workers.properties file but what changes need > to > be done in Jboss so that both instances are picked up by Apache load > balancer? > I tried changing Connector port="8009" to 8007 for the second instance but > it doesnt seem to work. > > Can anyone please help me out with this? > > Regards, > Nilesh > -- > View this message in context: > http://www.nabble.com/Apache-with-multiple-instance-of-jboss-on-same-server-tp23979597p23979597.html > Sent from the Apache HTTP Server - Users mailing list archive at > Nabble.com. > > > - > The official User-To-User support forum of the Apache HTTP Server Project. > See http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > " from the digest: users-digest-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >
Re: [us...@httpd] Stable Release of Apache
I see that apache 2.2.11 has been released but how do I find out if that's a stable release and something I can consider deploying in production? On Wed, Jun 10, 2009 at 10:17 PM, William A. Rowe, Jr. wrote: > Mohit Anchlia wrote: >> We are using Apache 2.2. How can I find which one is most recent >> stable version? I am trying to determine if we need to upgrade Apache. > > Have you visited http://httpd.apache.org recently? > > - > The official User-To-User support forum of the Apache HTTP Server Project. > See http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > " from the digest: users-digest-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > > - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [us...@httpd] Stable Release of Apache
On Thu, 2009-06-11 at 07:57 -0700, Mohit Anchlia wrote: > I see that apache 2.2.11 has been released but how do I find out if > that's a stable release and something I can consider deploying in > production? All releases of apache are stable releases; that is the definition of a release. The apache project don't release the unstable versions (eg the 2.1 and 2.3 branches). The version of apache you should be running is almost always the most recently released version. We always do, each release has important security fixes, which is the normal reason for a new release (very few new features get added to apache in a stable branch). Whether it works nicely with your infrastructure or not is something that can only be determined by you yourself though. Be sure to test. Cheers Tom - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [us...@httpd] Stable Release of Apache
Thanks. So if I already have some earlier version of 2.2 installed then does the apache install upgrades by applying patch or is it a new installation? On Thu, Jun 11, 2009 at 8:15 AM, Tom Evans wrote: > On Thu, 2009-06-11 at 07:57 -0700, Mohit Anchlia wrote: >> I see that apache 2.2.11 has been released but how do I find out if >> that's a stable release and something I can consider deploying in >> production? > > All releases of apache are stable releases; that is the definition of a > release. The apache project don't release the unstable versions (eg the > 2.1 and 2.3 branches). > > The version of apache you should be running is almost always the most > recently released version. We always do, each release has important > security fixes, which is the normal reason for a new release (very few > new features get added to apache in a stable branch). > > Whether it works nicely with your infrastructure or not is something > that can only be determined by you yourself though. Be sure to test. > > Cheers > > Tom > > > - > The official User-To-User support forum of the Apache HTTP Server Project. > See http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > " from the digest: users-digest-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > > - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [us...@httpd] Apache with multiple instance of jboss on same server
Sushant Gulati wrote: ... This list does not allow discussions about Jboss configuration. It is not that the list does not /allow/ discussions about JBoss. It is that JBoss is another software product, for which people here are probably not competent. And they know it, so they do not want to give bad recommendations. Send a seperate email regarding JBoss to me/JBoss discussion groups. That is a good recommendation, because as far as JBoss is concerned, the OP will get much better answers there. Once you are able to run multiple Jboss instances, then we can come back to this list with details regarding JBoss+apache connection using mod_jk. mod_jk is really part of the Apache Tomcat project, so the Tomcat list may be a better place. The Tomcat website is where you will find the mod_jk documentation, which is always a good place to start. http://tomcat.apache.org/connectors-doc/ There are how-to's, a wiki, example configurations etc.. - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [us...@httpd] Apache with multiple instance of jboss on same server
Hey Andre, Thanks a lot for your suggestions. Nilesh, Always, please check the official links like the one's suggested by Andre. They are always the best place to start. Hope you can figure out the error in the configuration, which I am sure would be minor. Otherwise we are all here to help each other. Regards, Sushant On Thu, Jun 11, 2009 at 9:11 PM, André Warnier wrote: > Sushant Gulati wrote: > ... > This list does > >> not allow discussions about Jboss configuration. >> > > It is not that the list does not /allow/ discussions about JBoss. > It is that JBoss is another software product, for which people here are > probably not competent. And they know it, so they do not want to give bad > recommendations. > > Send a seperate email > >> regarding JBoss to me/JBoss discussion groups. >> > > That is a good recommendation, because as far as JBoss is concerned, the OP > will get much better answers there. > > Once you are able to run multiple Jboss instances, then we can come back >> to >> this list with details regarding JBoss+apache connection using mod_jk. >> > > mod_jk is really part of the Apache Tomcat project, so the Tomcat list may > be a better place. The Tomcat website is where you will find the mod_jk > documentation, which is always a good place to start. > http://tomcat.apache.org/connectors-doc/ > There are how-to's, a wiki, example configurations etc.. > > > - > The official User-To-User support forum of the Apache HTTP Server Project. > See http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > " from the digest: users-digest-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >
Re: [us...@httpd] Stable Release of Apache
On Thu, 2009-06-11 at 08:24 -0700, Mohit Anchlia wrote: > Thanks. So if I already have some earlier version of 2.2 installed > then does the apache install upgrades by applying patch or is it a new > installation? No, if you are just downloading the tarball from httpd.apache.org, then it is a new installation. Your distribution may provide an easier update path though. Be careful if you just install over the top, any files from the old version that don't exist in the new version would stay on disk. It is often easier to preserve the conf, completely remove the original apache install, and then reinstall. Obviously, this is just if you are doing it from source. It is much preferred to use your distributions package management to upgrade it. Cheers Tom - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
[us...@httpd] httpd.exe - memory leak
Hi All, I am using Apache 2.2.11 on windows 2003 server. I am noticing that the memory used by httpd.exe is keep on increasing and one point of time, ( I saw it went up to 1.8GB) the child process got terminated and span a new process. Around 2 minutes, Apache won't respond and then It functions normally. I am not using php or mysql. Can someone tell me what is "status 3221225477" and guide me for a fix? Thu Jun 11 16:43:55 2009] [notice] Parent: child process exited with status 3221225477 -- Restarting. [Thu Jun 11 16:43:55 2009] [notice] Apache/2.2.11 (Win32) DAV/2 mod_ssl/2.2.11 OpenSSL/0.9.8i mod_jk/1.2.28 configured -- resuming normal operations [Thu Jun 11 16:43:55 2009] [notice] Server built: Dec 10 2008 00:10:06 [Thu Jun 11 16:43:55 2009] [notice] Parent: Created child process 4988 Thanks, Chris. - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [us...@httpd] Stable Release of Apache
Tom Evans wrote:
> On Thu, 2009-06-11 at 07:57 -0700, Mohit Anchlia wrote:
>> I see that apache 2.2.11 has been released but how do I find out if
>> that's a stable release and something I can consider deploying in
>> production?
>
> All releases of apache are stable releases; that is the definition of a
> release. The apache project don't release the unstable versions (eg the
> 2.1 and 2.3 branches).
Well, mostly correct. We do 'release' 2.1, 2.3 branches (development or
unstable, as you call it) by identifying them as -alpha or -beta.
There would be no 'stable' -alpha or -beta designations, when the branch
reaches maturity, it is given the next even-numbered revision, e.g. 2.4
or 3.0, and won't be identified as either -alpha or -beta.
OR quoting the web site...
"The Apache HTTP Server Project is proud to announce the release of version
2.2.11 of the Apache HTTP Server ("Apache"). This version is principally a
bugfix release."
"This version of Apache is a major release and the start of a new stable
branch, and represents the best available version of Apache HTTP Server. New
features include Smart Filtering, Improved Caching, AJP Proxy, Proxy Load
Balancing, Graceful Shutdown support, Large File Support, the Event MPM, and
refactored Authentication/Authorization."
I guess it's a little misleading, 2.2 certainly isn't "new" anymore, and
quoting the actual 2.2.11 announcement file;
"The Apache Software Foundation and the Apache HTTP Server Project are
pleased to announce the release of version 2.2.11 of the Apache HTTP Server
("Apache")."
"This version of Apache is principally a bug fix release."
"We consider this release to be the best version of Apache available, and
encourage users of all prior versions to upgrade."
So there's the message that should actually be on the main site :) cc'ing
docs@ so they can take a look at this and contribute an appropriate solution
to the confusion.
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
" from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
Re: [us...@httpd] Stable Release of Apache
Thanks. So I am little confused if I should wait for a while for
Apache 3.0 or take this as a stable release and upgrade from Apache
2.2.
On Thu, Jun 11, 2009 at 12:33 PM, William A. Rowe,
Jr. wrote:
> Tom Evans wrote:
>> On Thu, 2009-06-11 at 07:57 -0700, Mohit Anchlia wrote:
>>> I see that apache 2.2.11 has been released but how do I find out if
>>> that's a stable release and something I can consider deploying in
>>> production?
>>
>> All releases of apache are stable releases; that is the definition of a
>> release. The apache project don't release the unstable versions (eg the
>> 2.1 and 2.3 branches).
>
> Well, mostly correct. We do 'release' 2.1, 2.3 branches (development or
> unstable, as you call it) by identifying them as -alpha or -beta.
>
> There would be no 'stable' -alpha or -beta designations, when the branch
> reaches maturity, it is given the next even-numbered revision, e.g. 2.4
> or 3.0, and won't be identified as either -alpha or -beta.
>
> OR quoting the web site...
>
> "The Apache HTTP Server Project is proud to announce the release of version
> 2.2.11 of the Apache HTTP Server ("Apache"). This version is principally a
> bugfix release."
>
> "This version of Apache is a major release and the start of a new stable
> branch, and represents the best available version of Apache HTTP Server. New
> features include Smart Filtering, Improved Caching, AJP Proxy, Proxy Load
> Balancing, Graceful Shutdown support, Large File Support, the Event MPM, and
> refactored Authentication/Authorization."
>
> I guess it's a little misleading, 2.2 certainly isn't "new" anymore, and
> quoting the actual 2.2.11 announcement file;
>
> "The Apache Software Foundation and the Apache HTTP Server Project are
> pleased to announce the release of version 2.2.11 of the Apache HTTP Server
> ("Apache")."
>
> "This version of Apache is principally a bug fix release."
>
> "We consider this release to be the best version of Apache available, and
> encourage users of all prior versions to upgrade."
>
> So there's the message that should actually be on the main site :) cc'ing
> docs@ so they can take a look at this and contribute an appropriate solution
> to the confusion.
>
> -
> The official User-To-User support forum of the Apache HTTP Server Project.
> See http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> " from the digest: users-digest-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
>
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
" from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
Re: [us...@httpd] HTTP server scalability
Thank you Andrew and Tom,
Thank you for your insightful replies. These have definitely helped me in
understanding the major issues.
At this moment I can not understand "How a 'Connecton' is passed from parent
process to child process."
My understanding is
"a connection is a combination of (IP address + port.) and the parent
process listens at one such address or multiple such addresses in virtual
host interfaces."
Let us assume the parent process is listening to only one such address i.e.
(IP address + port). Then if this connection is passed to the child then
this connection must be blocked and this is the only connection which will
be multiplexed among several child processes as welll parent process. My
point is that concurrency can not be achieved on a single connection (IP
address + port) unless I am missing something fundemental about the
definition of "Connection."
Secondly if a connection is passed to the child then once again the child
process will have to make a three way handshake to the original client to
service the request.
I hope Andrew or someone from the group can clear my doubts.
Thanks.
Nagrik
On Wed, Jun 10, 2009 at 2:41 PM, André Warnier wrote:
> Complementary to what you will find in the on-line Apache documentation at
> http://httpd.apache.org, and painted with a very wide brush :
>
> When you start Apache, a single main Apache process is started.
> It reads and checks the configuration, and loads a series of core and
> add-on modules, as per your configuration.
>
> When it is done with that phase, it starts either a number of child
> processes (in the "prefork" type of setup), or a number of "children
> threads" (in the "worker" type of setup).
>
> Each of those is identical to the main Apache process that was built
> according to the configuration, but from now on the "main" process and the
> "children" will do different things.
>
> The "main" process opens the listening TCP port (or ports), as described in
> the "Listen" configuration directive(s), and starts waiting for connections
> to that (or these) port(s).
> When a connection comes in, it looks in the pool of available children
> processes/threads to find one that is inactive. If it finds one, it passes
> the opened TCP connection to that child/thread, and goes back to listen for
> more new connections on the server listening port (typically, port 80).
>
> The selected child/thread now "has" this TCP connection, and it reads and
> handles the HTTP request that came in on that connection. While it is doing
> that, it is "busy", and the main process will not give it another connection
> to handle.
>
> In the meantime, if another client connection happens to the main listening
> port, the main process will do the same again, this time finding another
> "idle" (available, not doing anything at the moment) child process/thread to
> pass this new connection to.
>
> When the child/thread is done with processing a request, it lets the main
> Apache process know that it is idle (free) again, ready to handle another
> connection if one is pending.
>
> The main Apache process does not handle requests. Its job is to listen for
> connections on the listening server port, accept these connections, and pass
> them on to children processes/threads for processing.
> In addition, it manages the pool of children processes/threads. As the
> load varies, the main Apache process may decide to start more children
> processes/threads, or to kill off some that really have nothing to do.
> This is controlled to some extent by a number of Apache configuration
> directives, such as the ones you find here :
> http://httpd.apache.org/docs/2.2/mod/directives.html
> (look for the directives starting in general with Max.. or Min.., and
> browse around)
>
> When the main Apache process receives the command to shut down, it normally
> lets each busy child finish their current request, then kills them off, then
> exits itself.
>
> The following is not specific to Apache, but relevant.
>
> The listening TCP socket has a "wait queue". That means, if a client new
> connection occurs before Apache has had time to accept the previous one and
> hand it over to a child, the new connection will not be rejected right away,
> it will wait a while. As soon as the main Apache process is done with
> passing the previous onnection to a child, it will pick up the first of
> these waiting connections, accept it, etc...
> Then the next waiting one if any.
> The maximum length of this queue varies; it is a TCP-level parameter.
> If the rate of incoming connections is so high that Apache cannot cope, the
> queue will get longer, up to this limit. If a new connection comes in when
> the limit of waiting ones is already reached, it will be rejected ("the
> server refused the connection").
>
> This is how a webserver like Apache handles multiple requests
> "simultaneously". It does not really accept new connections simultaneously,
> but accepting a connection a
[us...@httpd] Intermittent problems with mod_proxy, authentication, and Azureus HTML WebUI
Good afternoon, I run a variety of programs and services that present information or configuration via a web interface (tivowebplus, mlnet, sabnzbd, transmission, etc). Rather than every program presenting its own web server on a different port or even a different host (6886 for Vuze, 9091 for Transmission, 4080 for mlnet, etc), I'm using Apache's mod_proxy to access them via my existing web server and add authentication. Transmission, mlnet, sabnzbd, and my tivo's all proxy and authenticate seamlessly. However, the "Azureus HTML WebUI" plugin fails most of the time when loaded through the proxy with authentication, either displaying pages with broken images, broken CSS files, or the ever- informative "d14:failure reason29:String index out of range: -1e". Sometimes it loads perfectly, although very rarely. When I connect without the authentication block in the config, it works every time. If anyone sees anything amiss, by all means please let me know. Thanks, - Joshua Ochs Mac OS X 10.5.7 Client Apache/2.2.11 LoadModule proxy_html_modulelibexec/apache2/ mod_proxy_html.so ProxyRequests Off Order deny,allow Allow from all AuthName "Proxy Access" AuthType Digest AuthUserFile "/Library/WebServer/var/users.digest" Require valid-user ProxyPass /vuze/ http://127.0.0.1:6886/ ProxyPassReverse/vuze/ http://127.0.0.1:6886/ ProxyPass /transmission http://127.0.0.1:9091/transmission ProxyPassReverse/transmission http://127.0.0.1:9091/transmission ProxyPass /tivo http://tivo ProxyPassReverse/tivo http://tivo ProxyPass /tivo2 http://tivo2 ProxyPassReverse/tivo2 http://tivo2 ProxyPass /mlnet http://127.0.0.1:4080 ProxyPassReverse/mlnet http://127.0.0.1:4080 ProxyPass /news http://127.0.0.1:8080/sabnzbd ProxyPassReverse/news http://127.0.0.1:8080/sabnzbd - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [us...@httpd] Stable Release of Apache
Where can I get Apache that runs on 64bit linux? Is it available somewhere?
On Thu, Jun 11, 2009 at 1:31 PM, Mohit Anchlia wrote:
> Thanks. So I am little confused if I should wait for a while for
> Apache 3.0 or take this as a stable release and upgrade from Apache
> 2.2.
>
> On Thu, Jun 11, 2009 at 12:33 PM, William A. Rowe,
> Jr. wrote:
>> Tom Evans wrote:
>>> On Thu, 2009-06-11 at 07:57 -0700, Mohit Anchlia wrote:
I see that apache 2.2.11 has been released but how do I find out if
that's a stable release and something I can consider deploying in
production?
>>>
>>> All releases of apache are stable releases; that is the definition of a
>>> release. The apache project don't release the unstable versions (eg the
>>> 2.1 and 2.3 branches).
>>
>> Well, mostly correct. We do 'release' 2.1, 2.3 branches (development or
>> unstable, as you call it) by identifying them as -alpha or -beta.
>>
>> There would be no 'stable' -alpha or -beta designations, when the branch
>> reaches maturity, it is given the next even-numbered revision, e.g. 2.4
>> or 3.0, and won't be identified as either -alpha or -beta.
>>
>> OR quoting the web site...
>>
>> "The Apache HTTP Server Project is proud to announce the release of version
>> 2.2.11 of the Apache HTTP Server ("Apache"). This version is principally a
>> bugfix release."
>>
>> "This version of Apache is a major release and the start of a new stable
>> branch, and represents the best available version of Apache HTTP Server. New
>> features include Smart Filtering, Improved Caching, AJP Proxy, Proxy Load
>> Balancing, Graceful Shutdown support, Large File Support, the Event MPM, and
>> refactored Authentication/Authorization."
>>
>> I guess it's a little misleading, 2.2 certainly isn't "new" anymore, and
>> quoting the actual 2.2.11 announcement file;
>>
>> "The Apache Software Foundation and the Apache HTTP Server Project are
>> pleased to announce the release of version 2.2.11 of the Apache HTTP Server
>> ("Apache")."
>>
>> "This version of Apache is principally a bug fix release."
>>
>> "We consider this release to be the best version of Apache available, and
>> encourage users of all prior versions to upgrade."
>>
>> So there's the message that should actually be on the main site :) cc'ing
>> docs@ so they can take a look at this and contribute an appropriate solution
>> to the confusion.
>>
>> -
>> The official User-To-User support forum of the Apache HTTP Server Project.
>> See http://httpd.apache.org/userslist.html> for more info.
>> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
>> " from the digest: users-digest-unsubscr...@httpd.apache.org
>> For additional commands, e-mail: users-h...@httpd.apache.org
>>
>>
>
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
" from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
RE: [us...@httpd] Stable Release of Apache
> -Original Message- > From: Mohit Anchlia [mailto:mohitanch...@gmail.com] > Sent: Thursday, 11 June, 2009 14:17 > To: users@httpd.apache.org > Subject: Re: [us...@httpd] Stable Release of Apache > > Where can I get Apache that runs on 64bit linux? Is it > available somewhere? > Yes. Download the source and compile it: http://httpd.apache.org/download.cgi Or your distribution probably has packages pre-compiled. So for example, on Debian stable one would try `apt-get install apache2` - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
[us...@httpd] redirect webdav traffic from dmz to server inside firewall?
I have been trying to determine the proper configuration for a problem unsuccessfully. I have tried many online resources, but haven't been able to put the lid on this problem. My scenario: One server is running Apache in a dmz. Another server is running Apache inside a firewall, and is configured for webdav. I am trying to use mod_rewrite (or whatever config will accomplish this), but I must be missing something. I have tried virtual hosts, .htaccess files in /htdocs/en-us/webdav and /htdocs/en-us/webdav/readwrite, redirect rules, etc. Webdav is configured on the server inside the firewall, and works fine from inside the firewall. Webdav is not configured on the server in the dmz. I have also tried using port 81 for webdav. An example .htaccess file from htdocs/en-us/webdav/readwrite: Options +FollowSymlinks RewriteEngine on RewriteRule ^/$ http://192.168.124.139/webdav The two servers can ping each other successfully. It would be great to force everything to port 443, but even port 80 would be good, at this point. Thanks, Brent Friedman - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
