A few things come to mind that you could try:
Tomcat Max thread count should be higher than the expected number of max client in httpd. The tomcat threads may not clean up as quickly as the httpd threads and you may need more than one tomcat thread per httpd thread. Also, set a minimum spare thread count so, there is a thread ready to handle the next request from apache.
Change your "localhost" references to 127.0.0.1, I have had issues with this, mostly on windows boxes, where setting it to the local ip address just work better.
Use mod_jk instead of mod_proxy_ajp or use mod_proxy_http and http listener on the tomcat. I personally recommend mod_jk. It is a bit more complex to setup compared to mod_proxy_ajp but, if you look at the examples and read the manual on the tomcat website it is not difficult at all. Mod_jk also has connection pooling between apache and tomcat which should give you a performance boost.
Update tomcat, JIRA 6.1.7 ships with tomcat 7, I can't see a reason to stay on tomcat 6 with jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.