Extreme slowness in jira, we could see many "java.net.SocketTimeoutException: Read timed out " Exception in catalina log ??

[Vijayabhaskar Jella]

Hi All,

We are facing Extreme slowness in jira most often and most of the times it is not connecting to server.

We could see many "java.net.SocketTimeoutException: Read timed out " Exception in catalina log , Please help me on this to resolve this issue ????

[richie_gee]

It could be caused by mailing queue building up causing performance issue, since you mention socket timeout error exception:

https://confluence.atlassian.com/display/JIRAKB/Read+Timed+Out+Error+When+Sending+Outbound+Mail+from+JIRA

Mind to check you mail queue and perform manual flushing?

Perhaps check your memory allocation is sufficient or not.

Or generate full support zip (Administration > System > Atlassian Support Tool > Support Zip) and create an issue at support.atlassian.com for the engineers to assist you further on this.

Hope this helps :)

[Vijayabhaskar Jella]

Thanks for your valuable reply

, its helped a lot.

[MatthewC]

1. Switch on DEBUG log level
2. Switch on profiling
3. have a read of the knowledge base https://confluence.atlassian.com/display/JIRAKB/Crashes+and+Performance+Issues+Troubleshooting
4. What size is your server? How much data? How many users?
5. Read your logs
6. Where is it hosted?
7. How is it hosted? Physical, VM?
8. Are there other network problems
9. Where is your DB?
10. Come back to us when you have some details ;-)

[Radu Dumitriu]

This is usually caused by:

1. bad connections between Jira and the DB
2. bad connections between clients (browsers) and JIRA
3. faulty proxy configurations, bad setup of network interfaces (network loops, IP clashing, i.e. 1 computer on the local network have the same address as JIRA or DB)

[hsuhailah]

Could you explain a bit more on this slowness? Is it on project creation, view, etc?

I would suggest to upload the full logs here so that we could learn more about the issue or you can directly create a support ticket at https://support.atlassian.com (including the logs) and our support engineer will attend to the issue.