This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
I'm having some issues with my Tomcat setup. Quite erraticly, and I think when traffic is pretty high, Tomcat refuses to accept connections from mod_jk on port 8009. The setup is:
I know that my application running on Tomcat 4.1 is quite slow, and so it is possible that connections are piling up too quickly for Tomcat to handle. I've had an experiment with setting timeout values at both ends but this is having little effect.
From the JKStatus monitor, as soon as we start Apache 2.2 we see the number of Busy connections going up rapidly. When it reaches 64, it is game over. At this point, we get many items in the mod_jk log file like the following:
[Tue Jul 14 13:12:14.953 2009] [4224:4244] [error] jk_ajp_common.c (2426): (worker1) connecting to tomcat failed.
[Tue Jul 14 13:12:14.953 2009] [4224:1164] [error] jk_lb_worker.c (1432): All tomcat instances failed, no more workers left
[Tue Jul 14 13:12:15.062 2009] [4224:4100] [error] jk_ajp_common.c (1467): (worker1) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
Tomcat will still respond to requests directly through port 8080 at this time. Our mod_jk configuration includes such directives as...