'org.apache.jasper.JasperException Unable to compile class for JSP' or Workflow Actions Inaccessible

Still need help?

The Atlassian Community is here for you.

Ask the community


One or both of the following conditions may exist:

  1. Workflow actions may be inaccessible
  2. JIRA applications may throw exceptions on screen

The following appears in the atlassian-jira.log:

2007-12-06 10:55:05,327 http-8080-Processor20 ERROR [500ErrorPage] Exception caught in 500 page Unable to compile class for JSP
org.apache.jasper.JasperException: Unable to compile class for JSP
	at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:572)
	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:305)


The Tomcat container caches .java and .class files generated by the JSP parser they are used by the web application. Sometimes these get corrupted or cannot be found. This may occur after a patch or upgrade that contains modifications to JSPs.


  1. Delete the contents of the <JIRA_INSTALL>/work folder if using standalone JIRA or <CATALINA_BASE>/work if using EAR/WAR installation .
  2. Verify the user running the JIRA application process has Read/Write permission to the <JIRA_INSTALL|CATALINA_BASE>/work directory.
  3. Restart the JIRA application container to rebuild the files.
Last modified on Mar 30, 2016

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.