症状

When creating an new Jira issue from the UI using the Create button from the top bar menu, the following happens:

• the create issue screen appears and the user can fill in all the fields
• once the user clicks on the Create button at the bottom of create issue screen, the following happens:
  • the create issue screen remains open, and we can see a spinning wheel
  • after a few minutes:
    • the spinning wheel stops but the "Create issue" screen does not close
    • the user has to click on the cancel button to leave this screen
    • the "status 0" error is thrown in the console logs
  • the issue is actually created and can be found when searching for it in the issue search page

診断

• The impacted Jira instance:
  • is usually a Dev/Test instance, where an XML backup was imported from a Production Jira instance
  • contains several application links to other applications (Confluence, etc...), but cannot access these applications

• The catalina.out file (or thread dumps) reveal a long running thread similar to the one below:

  02-Mar-2021 15:29:35.091 WARNING [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [https-jsse-nio-8443-exec-74 url: /secure/QuickCreateIssue.jspa; user: XXXXXXXX] (id=[30471]) has been active for [123,308] milliseconds (since [3/2/21 3:27 PM]) to serve the same request for [<JIRA_BASE_URL>/secure/QuickCreateIssue.jspa?decorator=none] and may be stuck (configured threshold for this StuckThreadDetectionValve is [120] seconds). There is/are [14] thread(s) in total that are monitored by this Valve and may be stuck.
  	java.lang.Throwable
  		at java.net.SocketInputStream.socketRead0(Native Method)
  		at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
  		at java.net.SocketInputStream.read(SocketInputStream.java:171)
  		at java.net.SocketInputStream.read(SocketInputStream.java:141)
  		at org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:137)
  		at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:153)
  		at org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:282)
  		at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:138)
  		at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56)
  		at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259)
  		at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163)
  		at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:165)
  		at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273)
  		at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
  		at org.apache.http.impl.execchain.MainClientExec.createTunnelToTarget(MainClientExec.java:473)
  		at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:398)
  		at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)
  		at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
  		at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
  		at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)
  		at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
  		at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
  		at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:101)
  		at com.atlassian.sal.core.net.HttpClientRequest.execute(HttpClientRequest.java:75)
  		at com.atlassian.plugins.rest.module.jersey.JerseyRequest.execute(JerseyRequest.java:125)
  		at com.atlassian.applinks.core.auth.ApplicationLinkRequestAdaptor.execute(ApplicationLinkRequestAdaptor.java:45)
  		at com.atlassian.mywork.client.service.HostServiceImpl$3.apply(HostServiceImpl.java:279)
  		at com.atlassian.mywork.client.service.HostServiceImpl$3.apply(HostServiceImpl.java:268)
  		at com.atlassian.fugue.Option.filter(Option.java:301)
  		at com.atlassian.mywork.client.service.HostServiceImpl.updateHostAvailability(HostServiceImpl.java:182)
  		at com.atlassian.mywork.client.service.HostServiceImpl.lookupAppLink(HostServiceImpl.java:151)
  		at com.atlassian.mywork.client.service.HostServiceImpl.getRegisteredHost(HostServiceImpl.java:141)
  		at com.atlassian.mywork.client.service.ServiceSelectorImpl.isClientAvailable(ServiceSelectorImpl.java:252)
  
  

原因

When trying to create an issue, the Jira application tries to access the applications configured in the application links. Since the Jira application does not have access to the those applications, the request keeps going until it eventually times out, making the Create Issue screen spin the entire time.

ソリューション

2 possible solutions:

• Remove all the applications links from the impacted Jira instance
• Or ensure that this Jira instance has access to the other applications