Details
-
Bug
-
Resolution: Tracked Elsewhere
-
Medium
-
None
-
7.0.0
-
None
-
JIRA Calendar 2.1.11
-
7
-
Description
Summary
When upgrading JIRA to version 7.0, if the older instance had JIRA Calendar 2.1.11 installed, accessing the dashboard and multiple other pages results in 500 error.
The below exception may appear in the atlassian-jira.log.
2015-10-07 21:12:06,293 http-nio-8080-exec-10 ERROR admin 1272x26064x1 1pigghd 192.168.1.100 /secure/Dashboard.jspa [o.a.c.c.C.[.[.[.[jsp.decorators.general_002dhead_002dpre_jsp]] Servlet.service() for servlet jsp.decorators.general_002dhead_002dpre_jsp threw exception java.lang.NoSuchMethodError: com.atlassian.jira.security.JiraAuthenticationContext.getLoggedInUser()Lcom/atlassian/crowd/embedded/api/User; at com.atlassian.jira.ext.calendar.data.TipDataProvider.suppressTip(TipDataProvider.java:49) at com.atlassian.jira.ext.calendar.data.TipDataProvider.access$000(TipDataProvider.java:16) at com.atlassian.jira.ext.calendar.data.TipDataProvider$1.write(TipDataProvider.java:37) at com.atlassian.plugin.webresource.data.DataTagWriter.write(DataTagWriter.java:48) at com.atlassian.plugin.webresource.data.DataTagWriter.write(DataTagWriter.java:33) at com.atlassian.plugin.webresource.assembler.DefaultWebResourceSet.writeHtmlTags(DefaultWebResourceSet.java:82) at com.atlassian.plugin.webresource.assembler.DefaultWebResourceSet.writeHtmlTags(DefaultWebResourceSet.java:69) at com.atlassian.jira.plugin.navigation.HeaderFooterRendering.includeResources(HeaderFooterRendering.java:101) at jsp.decorators.general_002dhead_002dpre_jsp._jspService(general_002dhead_002dpre_jsp.java:122) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) ... 25 filtered at com.atlassian.jira.web.pagebuilder.AbstractJspDecorator.writeTemplate(AbstractJspDecorator.java:111) at com.atlassian.jira.web.pagebuilder.AbstractJspDecorator.writePreHead(AbstractJspDecorator.java:56) at com.atlassian.jira.web.pagebuilder.GeneralJspDecorator.writePreHead(GeneralJspDecorator.java:34) at com.atlassian.jira.web.pagebuilder.DefaultPageBuilder.flush(DefaultPageBuilder.java:87) at com.atlassian.jira.web.action.Dashboard.doExecute(Dashboard.java:195) ... 1 filtered at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:67) ... 7 filtered at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) ... 50 filtered at com.atlassian.greenhopper.jira.filters.ClassicBoardRouter.doFilter(ClassicBoardRouter.java:59) ... 159 filtered at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745)
Expected behavior
JIRA should load all pages correctly.
Actual behavior
Due to something broken in JIRA Calendar's methods, loading pages fail with a NoSuchMethodError thrown at the logs and a 500 error shown on-screen.
Workaround
Option #1
- Go to the below address;
http://<jira-address>/plugins/servlet/upm
- Update the JIRA Calendar Plugin to the latest version available;
Option #2
- Go to the below address;
http://<jira-address>/plugins/servlet/upm
- Disable the JIRA Calendar Plugin;