JIRA is not accessible after installing or updating the JavaMelody plugin

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

Problem

JIRA is not accessible after installing or updating the JavaMelody plugin.

The following exception is displayed while accessing JIRA, which is also visible in the logs:



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 more

Cause

This problem may happen if the wrong JAR file from JavaMelody was installed (e.g. javamelody-<version>.jar instead of jira-javamelody-<version>.jar).

Resolution

  1. Stop JIRA.
  2. Remove the wrong JAR file from the $JIRA_INSTALL/atlassian-jira/WEB-INF/lib/ folder.

  3. Download the correct JAR file from the vendor website (jira-javamelody-<version>.jar).

  4. Move the correct JAR file to the $JIRA_INSTALL/atlassian-jira/WEB-INF/lib/ folder and start JIRA.

Last modified on Sep 12, 2017

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.