JIRA is Unresponsive Threads Stuck

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

This Knowledge Base article was written specifically for the Atlassian Server platform and may be self applied.

問題

Any request made to JIRA just spins, waiting to load. After a while user may receive a timeout message from Tomcat or a Proxy.

Application logs do not contain any relevant information.  Access logs may have indication of 500 errors.

診断

診断ステップ

  • Running netstat -t indicates that all of Tomcat's connections are in the state: SYN_RECV

原因

When all all connections are stuck in SYN_RECV it indicates that the server has received the request, but is unable to respond. This is an indication that the server is overloaded, or simply does not have any extra threads. Possibilities include:

  • Denial of service attack (DOS)
  • Something is holding onto all of Tomcat's threads

ソリューション

If your server is victim of a DOS attack. Check with your network team/ISP. You may want to implement aggressive timeouts or rate limiting incoming connections.

Otherwise, you'll want to examine thread dumps to determine what is holding onto all of Tomcat's threads:

最終更新日: 2016 年 2 月 26 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.