Details
-
Bug
-
Resolution: Timed out
-
Low
-
None
-
5.1
-
Standalone JIRA 5.1. nginx 0.7.65 HTTP front-end running on a separate box. Both boxes are Ubuntu 10.04.4 LTS. conf/server.xml has been modified to bind to 0.0.0.0 instead of the default of 127.0.0.1.
-
5.01
-
3
-
Severity 3 - Minor
-
1
-
Description
We upgraded to JIRA 5.1 last night. After the upgrade, we began to have problems commenting on tickets. Chrome users reported spinning and a JIRA timeout message after 60s. One user reported no issues with FireFox.
I was able to consistently reproduce the issue with Chrome. The POST request did return HTTP 201 Created, but Chrome's network inspector indicated that the request was still spinning. The comments are successfully created, but the UI never seems to register the HTTP 201 response. I was able to fix the issue by disabling HTTP Keep-Alive in our nginx server.
Not sure if this is a new issue or something that's already covered elsewhere, but we've been running JIRA in this environment since the 4.x series. The problem only began occurring after the upgrade to 5.1.
