Degraded performance Customers may experience issues using Community search. Our team is investigating.
It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
Hello everybody and thanks in advance!
We are experiencing issues in our JIRA installations.
The final result is a 503 Internal Server Error visible for the users in the web browser that hapends in regular basis. A reload of the page use to work bringing back the application.
In the apache error log, each of those 503 errors print the following lines:
[error] ajp_read_header: ajp_ilink_receive failed
[error] (120006)APR does not understand this error code: proxy: dialog to [::1]:8010 (localhost) failed
And also:
[error] (32)Broken pipe: ajp_ilink_send(): send failed
[error] (70014)End of file found: ajp_ilink_receive() can't receive header
This is some information about our environment:
protocol="AJP/1.3"
connectionTimeout="20000"
redirectPort="8443" />
......
......
Is anybody experiencing the same? I've tried to align the number of threads in tomcat and the maxClients of apache with no success.
Thanks a lot for your help,
Borja Aparicio
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreHey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.