JIRA Software Automatically Disabled After Page Refresh
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
When a user installs JIRA software after upgrading from a pre JIRA 7 instance, they could run into an issue where they get the warning that they have JIRA Software installed but the plugin is not installed, with a button to install it appearing there.
The following appears in the atlassian-jira.log
07/04/2016 13: 43: 07.047 http-child-8091-exec-1906 WARN [c.atlassian.gzipfilter.GzipResponseWrapper] Was unable to create GzipResponseStream. Invalid gzip stream was sent in response body!
org.apache.catalina.connector.ClientAbortException: java.io.IOException: an established has been aborted by the software in your host computer connection.
at org.apache.catalina.connector.OutputBuffer.realWriteBytes (OutputBuffer.java:393)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer (ByteChunk.java:426)
at org.apache.catalina.connector.OutputBuffer.doFlush (OutputBuffer.java:342)
at org.apache.catalina.connector.OutputBuffer.flush (OutputBuffer.java:317)
at org.apache.catalina.connector.CoyoteOutputStream.flush (CoyoteOutputStream.java:110)
at java.util.zip.DeflaterOutputStream.flush (Unknown Source)
at com.atlassian.gzipfilter.GzipResponseStream.flush (GzipResponseStream.java:31)
at com.atlassian.gzipfilter.GzipResponseWrapper.finishResponse (GzipResponseWrapper.java:46)
at com.atlassian.gzipfilter.SelectingResponseWrapper.finishResponse (SelectingResponseWrapper.java:336)
... 17 filtered
at java.util.concurrent.ThreadPoolExecutor.runWorker (Unknown Source)
java.util.concurrent.ThreadPoolExecutor at $ Worker.run (Unknown Source)
org.apache.tomcat.util.threads.TaskThread at $ WrappingRunnable.run (TaskThread.java:61)
at java.lang.Thread.run (Unknown Source)
Caused by: java.io.IOException: it has been canceled by an established software on your host computer connection.
at sun.nio.ch.SocketDispatcher.write0 (Native Method)
at sun.nio.ch.SocketDispatcher.write (Unknown Source)
at sun.nio.ch.IOUtil.writeFromNativeBuffer (Unknown Source)
at sun.nio.ch.IOUtil.write (Unknown Source)
at sun.nio.ch.SocketChannelImpl.write (Unknown Source)
... 10 filtered
... 29 moreDiagnosis
Diagnostic Steps
- Check
Admin > Add-Ons > Managed Add-Onspage to see if the add-on is disabled and if yes, check if you have a plugin by the name JIRA Agile also installed. - Hence, you should see JIRA Agile and JIRA Software addons installed.
Cause
The problem is caused by the fact that the JIRA Agile is disrupting JIRA Software installation leading to it being disabled each time it is installed.
Workaround
- Stop JIRA
- Move the
JIRA HOME > Pluginsfolder to a new location as a backup. Restart JIRA.
- If all is okay, manually install all needed add-ons from the UI.