RE: jk 1.2.36 throwing 503/sendfull/cping errors
Thanks for the fix btw -Tony -Original Message- From: Mladen Turk [mailto:mt...@apache.org] Sent: Tuesday, May 29, 2012 11:39 AM To: users@tomcat.apache.org Subject: Re: jk 1.2.36 throwing 503/sendfull/cping errors On 05/29/2012 07:28 PM, Anthony J. Biacco wrote: Trunk works. Cool. That confirms my findings. We have release candidate at http://people.apache.org/~mturk/tomcat-connectors/jk-1.2.37/ Hope its gonna be voted by the end of this week. Regards -- ^TM - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: jk 1.2.36 throwing 503/sendfull/cping errors
Bug 53321 Checking out the trunk now. -Tony --- Manager, IT Operations Format Dynamics, Inc. P: 303-228-7327 F: 303-228-7305 abia...@formatdynamics.com http://www.formatdynamics.com -Original Message- From: Mladen Turk [mailto:mt...@apache.org] Sent: Sunday, May 27, 2012 10:27 PM To: users@tomcat.apache.org Subject: Re: jk 1.2.36 throwing 503/sendfull/cping errors On 05/27/2012 05:27 PM, Anthony J. Biacco wrote: Yeah, I can do that, thanks much. Cool. In between can you check the code from the trunk? Regards -- ^TM - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: jk 1.2.36 throwing 503/sendfull/cping errors
Trunk works. -Tony --- Manager, IT Operations Format Dynamics, Inc. P: 303-228-7327 F: 303-228-7305 abia...@formatdynamics.com http://www.formatdynamics.com -Original Message- From: Anthony J. Biacco [mailto:abia...@formatdynamics.com] Sent: Tuesday, May 29, 2012 11:21 AM To: Tomcat Users List Subject: RE: jk 1.2.36 throwing 503/sendfull/cping errors Bug 53321 Checking out the trunk now. -Tony --- Manager, IT Operations Format Dynamics, Inc. P: 303-228-7327 F: 303-228-7305 abia...@formatdynamics.com http://www.formatdynamics.com -Original Message- From: Mladen Turk [mailto:mt...@apache.org] Sent: Sunday, May 27, 2012 10:27 PM To: users@tomcat.apache.org Subject: Re: jk 1.2.36 throwing 503/sendfull/cping errors On 05/27/2012 05:27 PM, Anthony J. Biacco wrote: Yeah, I can do that, thanks much. Cool. In between can you check the code from the trunk? Regards -- ^TM - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --- ssi,-i e-ssi@mtpho oaioloasea:sse@mtpho
Re: jk 1.2.36 throwing 503/sendfull/cping errors
On 05/29/2012 07:28 PM, Anthony J. Biacco wrote: Trunk works. Cool. That confirms my findings. We have release candidate at http://people.apache.org/~mturk/tomcat-connectors/jk-1.2.37/ Hope its gonna be voted by the end of this week. Regards -- ^TM - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: jk 1.2.36 throwing 503/sendfull/cping errors
Yeah, I can do that, thanks much. -Tony -Original Message- From: Mladen Turk [mailto:mt...@apache.org] Sent: Saturday, May 26, 2012 2:35 AM To: users@tomcat.apache.org Subject: Re: jk 1.2.36 throwing 503/sendfull/cping errors On 05/25/2012 08:11 PM, Anthony J. Biacco wrote: GOOD loadbalancer (loadbalancer,app-03) BAD loadbalancer (app-03,loadbalancer) Could you open BZ entry for that? Although it works in most cases, it's an error and should be fixed. The point is that we can have both lb and standard workers with the same name because we allocate shared memory both by name and type. So, need a BZ entry so we can reference it as a regression from 1.2.35 Regards -- ^TM - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: jk 1.2.36 throwing 503/sendfull/cping errors
On 05/27/2012 05:27 PM, Anthony J. Biacco wrote: Yeah, I can do that, thanks much. Cool. In between can you check the code from the trunk? Regards -- ^TM - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: jk 1.2.36 throwing 503/sendfull/cping errors
On 05/25/2012 08:11 PM, Anthony J. Biacco wrote: GOOD loadbalancer (loadbalancer,app-03) BAD loadbalancer (app-03,loadbalancer) Could you open BZ entry for that? Although it works in most cases, it's an error and should be fixed. The point is that we can have both lb and standard workers with the same name because we allocate shared memory both by name and type. So, need a BZ entry so we can reference it as a regression from 1.2.35 Regards -- ^TM - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: jk 1.2.36 throwing 503/sendfull/cping errors
On Fri, May 25, 2012 at 6:45 AM, Mladen Turk mt...@apache.org wrote: On 05/24/2012 09:40 PM, Anthony J. Biacco wrote: I'm still puzzled as to why this behavior just changed between .35 and .36 OK, but if you follow the recommended configuration by making sure that workers which are members of lb are not listed inside worker.list, does it works? The question is, is this a recommendation or a restriction that should be enforced? Maybe a warning about this, apparently common, [mis-]configuration should be issued at module configuration time? Cheers Martin - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: jk 1.2.36 throwing 503/sendfull/cping errors
On 05/25/2012 11:28 AM, Martin Knoblauch wrote: On Fri, May 25, 2012 at 6:45 AM, Mladen Turkmt...@apache.org wrote: On 05/24/2012 09:40 PM, Anthony J. Biacco wrote: I'm still puzzled as to why this behavior just changed between .35 and .36 OK, but if you follow the recommended configuration by making sure that workers which are members of lb are not listed inside worker.list, does it works? The question is, is this a recommendation or a restriction that should be enforced? Maybe a warning about this, apparently common, [mis-]configuration should be issued at module configuration time? Hmm, I still didn't get the response if it works in case member workers are not in the worker.list. But you are right. Before 1.2.36 we just created another worker slot in shared memory. Now it's allocated 'by name' so it can create problems if the same name is declared both as standalone ajp13 worker and load balancer member. I'm sure that once we had 'must not be in worker.list', but someone changed that to 'should' inside http://tomcat.apache.org/connectors-doc/reference/workers.html (see balance_workers directive) Regards -- ^TM - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: jk 1.2.36 throwing 503/sendfull/cping errors
On Fri, May 25, 2012 at 1:29 PM, Mladen Turk mt...@apache.org wrote: On 05/25/2012 11:28 AM, Martin Knoblauch wrote: On Fri, May 25, 2012 at 6:45 AM, Mladen Turkmt...@apache.org wrote: On 05/24/2012 09:40 PM, Anthony J. Biacco wrote: I'm still puzzled as to why this behavior just changed between .35 and .36 OK, but if you follow the recommended configuration by making sure that workers which are members of lb are not listed inside worker.list, does it works? The question is, is this a recommendation or a restriction that should be enforced? Maybe a warning about this, apparently common, [mis-]configuration should be issued at module configuration time? Hmm, I still didn't get the response if it works in case member workers are not in the worker.list. I'm not the OP, although I believe he wrote so. But you are right. Before 1.2.36 we just created another worker slot in shared memory. Now it's allocated 'by name' so it can create problems if the same name is declared both as standalone ajp13 worker and load balancer member. This would explain the changed behaviour. As I said, if this is a non-no with 1.2.36+, there should be a watning in the logs, or an outright refusal to load. I'm sure that once we had 'must not be in worker.list', but someone changed that to 'should' inside http://tomcat.apache.org/connectors-doc/reference/workers.html (see balance_workers directive) Probably needs to be changed back, or a strong warning added. Cheers Martin - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: jk 1.2.36 throwing 503/sendfull/cping errors
On 05/24/2012 09:40 PM, Anthony J. Biacco wrote: I'm still puzzled as to why this behavior just changed between .35 and .36 OK, but if you follow the recommended configuration by making sure that workers which are members of lb are not listed inside worker.list, does it works? If I take the worker out of the worker list, then the loadbalancer works. But then accessing the worker by itself it doesn't. It seems to be based on the worker.list ordering Here's the behavior: worker.list=jkstatus,app-03,loadbalancer loadbalancer: does NOT work (503) app-03: works worker.list=jkstatus,loadbalancer,app-03 loadbalancer: works app-03: does NOT work (503) worker.list=jkstatus,loadbalancer loadbalancer: works app-03: does NOT work (500) -Tony - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: jk 1.2.36 throwing 503/sendfull/cping errors
I'm sure that once we had 'must not be in worker.list', but someone changed that to 'should' inside http://tomcat.apache.org/connectors-doc/reference/workers.html (see balance_workers directive) Probably needs to be changed back, or a strong warning added. And that's ok, if I need to change my config, then that's no problem. It does make it more complicated for me, but I don't care enough to gripe about it. :) I was just going by how I read the docs, so didn't know if it was a desired change or a bug. -Tony - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: jk 1.2.36 throwing 503/sendfull/cping errors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tony, On 5/25/12 12:07 PM, Anthony J. Biacco wrote: If I take the worker out of the worker list, then the loadbalancer works. But then accessing the worker by itself it doesn't. It seems to be based on the worker.list ordering Here's the behavior: worker.list=jkstatus,app-03,loadbalancer loadbalancer: does NOT work (503) app-03: works worker.list=jkstatus,loadbalancer,app-03 loadbalancer: works app-03: does NOT work (503) worker.list=jkstatus,loadbalancer loadbalancer: works app-03: does NOT work (500) What if you remove the jkstatus worker? What if you put jkstatus at the end of the list? I know we're grasping at straws, but you are not the only one who has this problem: 0.0.0.0 is showing up in a few places and we need to track it down. Thanks, - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+/tfQACgkQ9CaO5/Lv0PDFJQCfSkC5uWQG4iqJ84XOpNp3KV7I U5oAniHDeVa5mFQ4tv3s9Wnj8qcOFrmp =lAcB -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: jk 1.2.36 throwing 503/sendfull/cping errors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tony, On 5/25/12 12:07 PM, Anthony J. Biacco wrote: worker.list=jkstatus,app-03,loadbalancer loadbalancer: does NOT work (503) app-03: works worker.list=jkstatus,loadbalancer,app-03 loadbalancer: works app-03: does NOT work (503) worker.list=jkstatus,loadbalancer loadbalancer: works app-03: does NOT work (500) I can confirm that load-balancing works properly in my environment[1] with this workers.properties: worker.list=jk-status worker.jk-status.type=status # Template worker worker.template.type=ajp13 worker.template.host=localhost worker.template.connection_pool_timeout=60 worker.template.socket_timeout=300 worker.template.max_packet_size=65536 worker.list=crazy-lb worker.crazy-lb.type=lb worker.crazy-lb.balance_workers=worker23,worker03 worker.list=worker01 worker.worker01.reference=worker.template worker.worker01.port=8015 [more workers defined in exactly the same way] All worked as well as I expected (see below). - -chris [1] Environment: Debian Linux kernel 2.6.32 x86_64 Apache httpd 2.2.16-6 mod_jk 1.2.36 (just built it myself against httpd 2.2.16-6) Oracle Java 1.6.0_26-b03 (though not terribly relevant) Tomcat 7.0.27 and Tomcat 6.0.35 (I balanced two different TC versions and two different webapps... the results were not pretty but proved that mod_jk was working properly) -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+/udIACgkQ9CaO5/Lv0PAH1gCfd6Dqc3IoLUQzQTN0zFnINpko K+YAoMBkcEwxJP5tKhYG87I9XdFoChML =/OIp -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: jk 1.2.36 throwing 503/sendfull/cping errors
What if you remove the jkstatus worker? worker.list=app-03,loadbalancer app-03: works loadbalancer: does NOT work (503) worker.list=loadbalancer,app-03 app-03: does NOT work (503) loadbalancer: works What if you put jkstatus at the end of the list? worker.list=app-03,loadbalancer,jkstatus app-03: works loadbalancer: does NOT work (503) worker.list=loadbalancer,app-03,jkstatus app-03: does NOT work (503) loadbalancer: works -Tony Thanks, - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+/tfQACgkQ9CaO5/Lv0PDFJQCfSkC5uWQG4iqJ84XOpNp3K V7I U5oAniHDeVa5mFQ4tv3s9Wnj8qcOFrmp =lAcB -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: jk 1.2.36 throwing 503/sendfull/cping errors
GOOD loadbalancer (loadbalancer,app-03) [Fri May 25 11:52:52 2012] [24754:1138370880] [debug] wc_get_worker_for_name::jk_worker.c (115): found a worker loadbalancer [Fri May 25 11:52:52 2012] [24754:1138370880] [debug] wc_get_name_for_type::jk_worker.c (292): Found worker type 'lb' [Fri May 25 12:01:20 2012] [25030:1105992000] [debug] service::jk_lb_worker.c (1248): service worker=app-03 route=app-03 [Fri May 25 12:01:20 2012] [25030:1105992000] [info] service::jk_lb_worker.c (1254): FD: IP is 127.0.0.1 BAD loadbalancer (app-03,loadbalancer) [Fri May 25 11:52:52 2012] [24754:1138370880] [debug] wc_get_worker_for_name::jk_worker.c (115): found a worker loadbalancer [Fri May 25 11:52:52 2012] [24754:1138370880] [debug] wc_get_name_for_type::jk_worker.c (292): Found worker type 'lb' [Fri May 25 11:52:52 2012] [24754:1138370880] [debug] service::jk_lb_worker.c (1248): service worker=app-03 route=app-03 [Fri May 25 11:52:52 2012] [24754:1138370880] [info] service::jk_lb_worker.c (1254): FD: IP is 0.0.0.0 I'm getting the IP using inet_ntoa on the worker_inet_addr In both GOOD and BAD scenarios, jk_resolve has the right IP for the app-03 every time. So it's somewhere in between or right in jk_lb_worker.c -Tony --- Manager, IT Operations Format Dynamics, Inc. P: 303-228-7327 F: 303-228-7305 abia...@formatdynamics.com http://www.formatdynamics.com -Original Message- From: Anthony J. Biacco [mailto:abia...@formatdynamics.com] Sent: Friday, May 25, 2012 11:40 AM To: Tomcat Users List Subject: RE: jk 1.2.36 throwing 503/sendfull/cping errors What if you remove the jkstatus worker? worker.list=app-03,loadbalancer app-03: works loadbalancer: does NOT work (503) worker.list=loadbalancer,app-03 app-03: does NOT work (503) loadbalancer: works What if you put jkstatus at the end of the list? worker.list=app-03,loadbalancer,jkstatus app-03: works loadbalancer: does NOT work (503) worker.list=loadbalancer,app-03,jkstatus app-03: does NOT work (503) loadbalancer: works -Tony Thanks, - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+/tfQACgkQ9CaO5/Lv0PDFJQCfSkC5uWQG4iqJ84XOpNp3K V7I U5oAniHDeVa5mFQ4tv3s9Wnj8qcOFrmp =lAcB -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: jk 1.2.36 throwing 503/sendfull/cping errors
1.2.32 and 1.2.35 work fine. [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] jk_open_socket::jk_connect.c (609): trying to connect socket 22 to 0.0.0.0:0 Connecting to 0.0.0.0:0 ? Yeah, I balked at that too. [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] jk_open_socket::jk_connect.c (635): socket 22 [errno=107] connected getsockname fails with errno=107 (ENOTCONN) Fix your config. Please point out the workers.properties config line from my OP that's incorrect. I didn't change configs at all from 1.2.32-1.2.35-1.2.36. How could the config all of a sudden be incorrect with 1.2.36? The changelog doesn't mention anything about deprecated or changed parameters. -Tony - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: jk 1.2.36 throwing 503/sendfull/cping errors
Anthony J. Biacco wrote: Please point out the workers.properties config line from my OP that's incorrect. I didn't change configs at all from 1.2.32-1.2.35-1.2.36. How could the config all of a sudden be incorrect with 1.2.36? The changelog doesn't mention anything about deprecated or changed parameters. I don't know if it has anything to do with your problem, but workers.properties settings are: worker.list=jkstatus,app-03,loadbalancer - worker.template.port=8009 worker.template.type=ajp13 worker.template.lbfactor=1 worker.template.connection_pool_timeout=30 worker.template.connect_timeout=3 worker.template.recovery_options=4 worker.template.reply_timeout=31000 worker.template.socket_timeout=20 worker.template.socket_connect_timeout=5000 worker.template.ping_mode=A worker.template.ping_timeout=2 worker.app-03.host=127.0.0.1 worker.app-03.reference=worker.template worker.jkstatus.type=status worker.loadbalancer.sticky_session=1 worker.loadbalancer.type=lb worker.loadbalancer.balance_workers=app-03 - You have the worker app-03 referenced both as a worker in its own right, and as a balanced worker. Isn't this a bit strange ? Normally, if it is accessed via the balancer, you do not list it in workers.list. See http://tomcat.apache.org/connectors-doc/reference/workers.html, balance_workers - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: jk 1.2.36 throwing 503/sendfull/cping errors
You have the worker app-03 referenced both as a worker in its own right, and as a balanced worker. Isn't this a bit strange ? Normally, if it is accessed via the balancer, you do not list it in workers.list. I have it in the list because sometimes I reference a specific worker in the jkmount and sometimes the balancer. Maybe I'll have a balancer with app-01 and app-02 and under normal circumstances access the a balancer, but then maybe I'll need to test something and I want to send things to just app-01. So I'll point the jkmount to app-01. If I take it out of the worker.list I can't do that. In this particular environment's config I quoted it doesn't apply since I only have one worker, but in my prod environment it's like above with multiple workers. FWIW, if I point the jkmount to the specific worker (app-03) and not the loadbalancer it works. If I take the worker out of the worker.list as your suggest and point my jkmount to the loadbalancer works, but then I can't point jkmount to a specific worker, I'll get a 500 error and Could not find a worker for worker name=app-03 So to get it to work under the previous behavior, I'd have to have 2 workers. 1 worker entry if I want to use it directly (and put into the worker.list) and 1 worker entry if I want to use it in the loadbalancer. So basically I'm changing my config (which seems kind of wacky) to: worker.list=jkstatus,app-03-standalone,loadbalancer worker.app-03.host=127.0.0.1 worker.app-03.reference=worker.template worker.app-03-standalone.host=127.0.0.1 worker.app-03-standalone.reference=worker.template worker.jkstatus.type=status worker.loadbalancer.sticky_session=1 worker.loadbalancer.type=lb worker.loadbalancer.balance_workers=app-03 I'm still puzzled as to why this behavior just changed between .35 and .36 -Tony See http://tomcat.apache.org/connectors-doc/reference/workers.html, balance_workers - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: jk 1.2.36 throwing 503/sendfull/cping errors
On 05/24/2012 09:40 PM, Anthony J. Biacco wrote: I'm still puzzled as to why this behavior just changed between .35 and .36 OK, but if you follow the recommended configuration by making sure that workers which are members of lb are not listed inside worker.list, does it works? Regards -- ^TM - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: jk 1.2.36 throwing 503/sendfull/cping errors
Centos 5.8, x86_64, apache 2.2.22, java 1.6.0_32, tomcat 7.0.27, apr 1.4.6 (also happens on another machine with apache 2.2.21 and java 1.6.0_29, rest of the versions are the same) FWIW I also tried the following combos with the same effects: tomcat 7.0.25/jni 1.1.22/apr 1.4.5 tomcat 7.0.25/jni 1.1.22/apr 1.4.6 tomcat 7.0.26/jni 1.1.22/apr 1.4.6 -Tony Connecting apache to tomcat ajp, same machine. Once I upgraded to 1.2.36 I started receiving 503 errors when trying to access my webapps. 1.2.32 and 1.2.35 work fine. Tomcat catalina.out and access logs show nothing Jk log shows: [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] ajp_get_endpoint::jk_ajp_common.c (3154): acquired connection pool slot=0 after 0 retries [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] ajp_marshal_into_msgb::jk_ajp_common.c (626): ajp marshaling done [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] ajp_service::jk_ajp_common.c (2449): processing app-03 with 2 retries [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] ajp_send_request::jk_ajp_common.c (1623): (app-03) all endpoints are disconnected. [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] jk_open_socket::jk_connect.c (485): socket TCP_NODELAY set to On [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] jk_open_socket::jk_connect.c (574): timeout 20 set for socket=22 [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] jk_open_socket::jk_connect.c (609): trying to connect socket 22 to 0.0.0.0:0 [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] jk_open_socket::jk_connect.c (635): socket 22 [errno=107] connected [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] ajp_connection_tcp_send_message::jk_ajp_common.c (1183): sending to ajp13 pos=4 len=5 max=16 [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] ajp_connection_tcp_send_message::jk_ajp_common.c (1183): 12 34 00 01 0A 00 00 00 00 00 00 00 00 00 00 00 - .4.. [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] jk_shutdown_socket::jk_connect.c (732): About to shutdown socket 22 [errno=107] [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] jk_shutdown_socket::jk_connect.c (741): Failed sending SHUT_WR for socket 22 [errno=107] [Wed May 23 15:56:32 2012] [32504:1138178368] [info] ajp_connection_tcp_send_message::jk_ajp_common.c (1215): sendfull for socket 22 returned -32 (errno=32) [Wed May 23 15:56:32 2012] [32504:1138178368] [info] ajp_handle_cping_cpong::jk_ajp_common.c (902): can't send cping query [Wed May 23 15:56:32 2012] [32504:1138178368] [error] ajp_connect_to_endpoint::jk_ajp_common.c (1026): (app-03) cping/cpong after connecting to the backend server failed (errno=32) [Wed May 23 15:56:32 2012] [32504:1138178368] [error] ajp_send_request::jk_ajp_common.c (1629): (app-03) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=32) [Wed May 23 15:56:32 2012] [32504:1138178368] [info] ajp_service::jk_ajp_common.c (2622): (app-03) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1) I also noticed that a tcpdump shows 0 packets to and from on the lo interface httpd.conf settings are: JkWorkersFile /path/to/workers.properties JkWatchdogInterval 60 JkLogFile /path/to/GLOBAL-mod_jk.log JkLogLeveldebug JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkOptions +ForwardKeySize +ForwardURIProxy -ForwardDirectories JkRequestLogFormat %w %R %V %B %T %m %U %s JkShmFile logs/jk-runtime-status JkMount /webapp/* loadbalancer workers.properties settings are: worker.list=jkstatus,app-03,loadbalancer worker.template.port=8009 worker.template.type=ajp13 worker.template.lbfactor=1 worker.template.connection_pool_timeout=30 worker.template.connect_timeout=3 worker.template.recovery_options=4 worker.template.reply_timeout=31000 worker.template.socket_timeout=20 worker.template.socket_connect_timeout=5000 worker.template.ping_mode=A worker.template.ping_timeout=2 worker.app-03.host=127.0.0.1 worker.app-03.reference=worker.template worker.jkstatus.type=status worker.loadbalancer.sticky_session=1 worker.loadbalancer.type=lb worker.loadbalancer.balance_workers=app-03 server.xml settings are: Connector port=8009 protocol=AJP/1.3 maxThreads=1000 backlog=25 maxPostSize=4194304 enableLookups=false connectionTimeout=3 keepAliveTimeout=1 redirectPort=8443 / # netstat -anop | grep 8009 tcp0 0 0.0.0.0:80090.0.0.0:* LISTEN 30151/jsvc.exec off (0.00/0/0) -Tony --- Manager, IT Operations Format Dynamics, Inc. P: 303-228-7327 F: 303-228-7305 abia...@formatdynamics.com http://www.formatdynamics.com - To unsubscribe, e-mail:
Re: jk 1.2.36 throwing 503/sendfull/cping errors
On 05/24/2012 12:12 AM, Anthony J. Biacco wrote: Centos 5.8, x86_64, apache 2.2.22, java 1.6.0_32, tomcat 7.0.27, apr 1.4.6 (also happens on another machine with apache 2.2.21 and java 1.6.0_29, rest of the versions are the same) Connecting apache to tomcat ajp, same machine. Once I upgraded to 1.2.36 I started receiving 503 errors when trying to access my webapps. 1.2.32 and 1.2.35 work fine. [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] jk_open_socket::jk_connect.c (609): trying to connect socket 22 to 0.0.0.0:0 Connecting to 0.0.0.0:0 ? [Wed May 23 15:56:32 2012] [32504:1138178368] [debug] jk_open_socket::jk_connect.c (635): socket 22 [errno=107] connected getsockname fails with errno=107 (ENOTCONN) Fix your config. Regards -- ^TM - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
