JIRA is not accessible after installing or updating the JavaMelody plugin
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Summary
Problem
Jira is not accessible after installing or updating the JavaMelody plugin.
Environment
Jira Data Center
Diagnosis
The following exception is displayed while accessing JIRA, which is also visible in the logs:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
2015-04-24 14:50:19,395 http-bio-8641-exec-12 ERROR anonymous 890x29x1 a4gxb8 0:0:0:0:0:0:0:1 /secure/Dashboard.jspa [jira.web.filters.CommittedResponseHtmlErrorRecoveryFilter] Exception occurred after HTTP response was already committed: java.lang.IllegalStateException: getOutputStream() does not support decorators
org.apache.jasper.JasperException: java.lang.IllegalStateException: getOutputStream() does not support decorators
at org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:549)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:465)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
(...)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:724)
Caused by: java.lang.IllegalStateException: getOutputStream() does not support decorators
at com.atlassian.jira.web.filters.pagebuilder.PageBuilderResponseWrapper.getOutputStream(PageBuilderResponseWrapper.java:79)
at com.opensymphony.module.sitemesh.filter.PageResponseWrapper$4.create(PageResponseWrapper.java:105)
at com.opensymphony.module.sitemesh.filter.RoutableServletOutputStream.getDestination(RoutableServletOutputStream.java:35)
at com.opensymphony.module.sitemesh.filter.RoutableServletOutputStream.write(RoutableServletOutputStream.java:118)
at net.bull.javamelody.FilterServletOutputStream.write(FilterServletOutputStream.java:83)
at net.bull.javamelody.CounterResponseStream.write(CounterResponseStream.java:82)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
at java.io.PrintWriter.flush(PrintWriter.java:320)
at org.apache.jasper.runtime.JspWriterImpl.flush(JspWriterImpl.java:179)
at org.apache.jsp.secure.views.dashboard_jsp._jspService(dashboard_jsp.java:97)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
... 242 moreCause
This problem may happen if the wrong JAR file from JavaMelody was installed (e.g. javamelody-<version>.jar instead of jira-javamelody-<version>.jar).
Solution
Resolution
Stop JIRA.
Remove the wrong JAR file from the $JIRA_INSTALL/atlassian-jira/WEB-INF/lib/ folder.
Download the correct JAR file from the vendor website (jira-javamelody-<version>.jar).
Move the correct JAR file to the $JIRA_INSTALL/atlassian-jira/WEB-INF/lib/ folder and start JIRA.
Was this helpful?