On Oct 29, 2012, at 9:41 AM, Charles Richard wrote: > No firewall, all on one server. Right now, I'm thinking I'm either hitting > some type of tcp connection maximum or something is going on with Apache or > mod_jk.
Think you might be on the right track here. I just google'd "errno=24" and it came up with "Too many open files". Dan > If I just restart Apache, i can connect to Tomcat again which > tells me Tomcat wasn't down. > > Cheers, > Charles > > On Mon, Oct 29, 2012 at 10:39 AM, Daniel Mikusa <dmik...@vmware.com> wrote: > >> On Oct 29, 2012, at 8:37 AM, Charles Richard wrote: >> >>> Hi, >>> >>> I had a thread a while back but my configuration has changed and so has >> my >>> issue, so hence a new thread. >>> >>> My config: >>> >>> CentOS 5.8 >>> Apache 2.23 >>> 3 tomcat instances (6.0.30) with each ajp_port with a connectionTimeout >>> setting of 180000 >>> mod_jk 1.2.37 >>> >>> workers.properties: >>> >>> # Define 1 real worker using ajp13 >>> worker.list=worker1, worker2, worker3, lbworker >>> >>> # Set properties for worker1 (ajp13) >>> worker.worker1.type=ajp13 >>> worker.worker1.host=localhost >>> worker.worker1.port=8009 >>> worker.worker1.connection_pool_timeout=180 >>> worker.worker1.lbfactor=1 >>> worker.worker1.ping_mode=A >>> worker.worker1.socket_keepalive=true >>> >>> # Set properties for worker2 (ajp13) >>> worker.worker2.type=ajp13 >>> worker.worker2.host=localhost >>> worker.worker2.port=8010 >>> worker.worker2.connection_pool_timeout=180 >>> worker.worker2.lbfactor=1 >>> worker.worker2.ping_mode=A >>> worker.worker2.socket_keepalive=true >>> >>> # Set properties for worker3 (ajp13) >>> worker.worker3.type=ajp13 >>> worker.worker3.host=localhost >>> worker.worker3.port=8011 >>> worker.worker3.connection_pool_timeout=180 >>> worker.worker3.lbfactor=1 >>> worker.worker3.ping_mode=A >>> worker.worker3.socket_keepalive=true >>> >>> worker.lbworker.type=lb >>> worker.lbworker.balance_workers=worker1, worker2, worker3 >>> worker.lbworker.sticky_session=True >>> >>> I'm doing some performance tuning on our application and noticed a couple >>> of days ago that which a load of 1500 users, my threads in VisualVM would >>> turn white in a "off/unknown state" (can send a snapshot of this on >>> demand). Since then, I added the ping_mode and socket_keepalive setting >> in >>> my workers.properties file but that didn't seem to make a difference. >> All >>> i see in my mod_jk log is this: >>> >>> [Mon Oct 29 09:16:56 2012] [12205:47535048426352] [info] >>> ajp_handle_cping_cpong::jk_ajp_common.c (913): timeout in reply cpong >>> [Mon Oct 29 09:16:56 2012] [12205:47535048426352] [info] >>> ajp_maintain::jk_ajp_common.c (3289): (worker2) failed sending request, >>> socket -1 keepalive cping/cpong failure (errno=24) >>> [Mon Oct 29 09:18:36 2012] [10542:47535048426352] [info] >>> ajp_handle_cping_cpong::jk_ajp_common.c (913): timeout in reply cpong >>> [Mon Oct 29 09:18:36 2012] [10542:47535048426352] [info] >>> ajp_maintain::jk_ajp_common.c (3289): (worker2) failed sending request, >>> socket -1 keepalive cping/cpong failure (errno=24) >>> >>> Any idea what could be going on? >> >> Do you have a firewall between Apache HTTPD and your Tomcat instances? >> >> Dan >> >> >>> Thanks, >>> Charles >> >> >> --------------------------------------------------------------------- >> 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
