We are running Jira 4.3.4, standalone installation
Jira was running slow and then hanging for some of our users. This is what we were able to pull off the logs. We restarter Jira to fix the problem to get back up and running. Can you help with what might be causing this?
This was the log file
11:26:55 AM: David Armstrong/AGIS: May 4, 2012 11:15:13 AM org.apache.tomcat.util.net.JIoEndpoint$Acceptor run
SEVERE: Socket accept failed
java.net.SocketException: Too many open files
at java.net.PlainSocketImpl.socketAccept(Native Method)
Unfortunately, there could be a bunch of causes. For instance, if you’ve greatly increased the default timeout, all the logged-in, un-timed-out users could be consuming resources causing you to hit the open files limit. You could look at your system and see if you’ve done anything to the configuration that would increase the resources needed. Or you could just work around it by increasing the number of open files allowed.
Oh, there’s an article in the Atlassian knowledge base about this: http://confluence.atlassian.com/display/JIRAKB/Loss+of+Functionality+due+to+Too+Many+Open+Files+Error . That might help you.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG