Details
-
Bug
-
Resolution: Fixed
-
High
-
7.2.0, 7.3.0, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.7, 7.3.8, 7.4.1, 7.4.2, 7.5.0, 7.4.3, 7.4.5, 7.2.12, 7.6.0, 7.5.3, 7.4.6, 7.5.4, 7.6.1, 7.7.0, 7.6.4, 7.3.9, 7.7.2, 7.7.1, 7.8.0, 7.9.0
-
7.02
-
121
-
Severity 1 - Critical
-
5,168
-
-
Description
Summary
Accessing a non-existent url in JIRA during startup will break access to the instance until a restart is performed.
During the start the following error can be observed when the request is received:
2017-09-01 14:29:59,923 http-nio-8080-exec-9 ERROR - [o.a.c.c.C.[.[localhost].[/].[action]] Servlet.service() for servlet action threw exception java.lang.NullPointerException at com.atlassian.jira.config.webwork.DelegatingConfiguration.getImpl(DelegatingConfiguration.java:26) at webwork.config.Configuration.get(Configuration.java:44) at webwork.config.Configuration.getString(Configuration.java:54) at webwork.dispatcher.GenericDispatcher.<clinit>(GenericDispatcher.java:43) at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.prepareDispatcher(JiraWebworkActionDispatcher.java:196) ... 1 filtered at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) ... 54 filtered at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:748)
The following error will be thrown in the logging for every new request after the original null pointer above is hit, and the end user will be greeted with a 500 error:
2017-09-01 14:30:06,534 http-nio-8080-exec-10 ERROR - [o.a.c.c.C.[.[localhost].[/].[action]] Servlet.service() for servlet action threw exception java.lang.NoClassDefFoundError: Could not initialize class webwork.dispatcher.GenericDispatcher at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.prepareDispatcher(JiraWebworkActionDispatcher.java:196) at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165) ... 52 filtered at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:748)
Steps to Reproduce
- Start JIRA
- Make frequent requests to a url that does not exist on the JIRA instance while JIRA is still initializing (eg. localhost:PORT/something)
Expected Results
JIRA should start up normally.
Actual Results
JIRA throws an internal server error.
Notes
- Seems to be happening only in very specific environmental conditions (eg. Java version, installer type)
Workaround
- Block web access to the instance during start up to prevent the bad request from hitting JIRA during startup such as the following examples:
- Change the port in server.xml during startup or upgrade to avoid users unintentionally accessing URLs which may cause such problems
- Leverage a firewall on the server hosting JIRA to block the port during startup
- In cases where a reverse proxy or balancer is in front of JIRA this can be shut down during startup
NOTE: The same symptoms are sometimes seen due to corrupted plugin caches or /work directory. If troubleshooting this issue, clearing these directories may resolve the issue:
- /JIRA_HOME/plugins/.osgi-plugins/
- /JIRA_HOME/plugins/.bundled-plugins/
- /JIRA_INSTALL/work/
Attachments
Issue Links
- has a regression in
-
-
- Closed
-
- was split into
-
-
- Gathering Impact
-
- caused
-
HOT-72648 Loading...
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- relates to
-