Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-4220

JIRA becomes inacessible after upgrading JIRA Service Desk to 3.2.0.

XMLWordPrintable

      Summary

      JIRA becomes inacessible after upgrading JIRA Service Desk to 3.2.0.

      Environment

      • PostgreSQL 9.3

      Steps to Reproduce

      1. Install JIRA 7.0.10 or 7.1.9
      2. Install JIRA Service Desk 3.0.10 or 3.1.9
      3. Upgrade JIRA to 7.2.0
      4. Navigate to Cog Icon > Applications > Upgrade JIRA Service Desk to 3.2.0
      5. Navigate to any other page in JIRA.

      Expected Results

      JIRA should be accessible after the upgrade.

      Actual Results

      JIRA becomes inacessible, showing a 500 error with the following stack trace:

      Technical details
Log's referral number: 1949e8c6-a651-4a17-8ab8-d8f1b3666a10
Cause
Referer URL: http://localhost:8080/plugins/servlet/applications/versions-licenses
java.lang.RuntimeException: javax.servlet.ServletException: java.lang.IllegalArgumentException: Root page 'com.atlassian.jira.gadgets:dashboard-page' does not exist!
java.lang.RuntimeException: javax.servlet.ServletException: java.lang.IllegalArgumentException: Root page 'com.atlassian.jira.gadgets:dashboard-page' does not exist!
	at com.atlassian.web.servlet.plugin.DynamicAuthorizationServletForwarder.forward(DynamicAuthorizationServletForwarder.java:55) [?:?]
	at com.atlassian.web.servlet.plugin.DynamicAuthorizationServletForwarder.forwardSafely(DynamicAuthorizationServletForwarder.java:83) [?:?]
	at com.atlassian.web.servlet.plugin.SanitizingServletForwarder.forwardSafely(SanitizingServletForwarder.java:48) [?:?]
	at com.atlassian.web.servlet.plugin.RememberingServletForwarder.forwardSafely(RememberingServletForwarder.java:75) [?:?]
	at com.atlassian.web.servlet.plugin.ResolvingServletForwarder.forwardSafely(ResolvingServletForwarder.java:52) [?:?]
	at com.atlassian.web.servlet.plugin.request.RedirectInterceptingResponse.lambda$null$0(RedirectInterceptingResponse.java:43) [?:?]
	at java.util.Optional.map(Optional.java:215) [?:1.8.0_77]
	at com.atlassian.web.servlet.plugin.request.RedirectInterceptingResponse.lambda$sendRedirect$1(RedirectInterceptingResponse.java:43) [?:?]
	at java.util.Optional.flatMap(Optional.java:241) [?:1.8.0_77]
	at com.atlassian.web.servlet.plugin.request.RedirectInterceptingResponse.sendRedirect(RedirectInterceptingResponse.java:43) [?:?]
	at javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:138) [servlet-api.jar:?]
	at com.atlassian.core.filters.HeaderSanitisingResponseWrapper.sendRedirect(HeaderSanitisingResponseWrapper.java:85) [atlassian-core-5.0.6.jar:?]
(...)

      Notes

      • It doesn't look like anything breaks permanently. JIRA works fine after a restart.
      • Uninstalling JSD 3.0.10 on JIRA 7.2.0 before installing JSD 3.2.0 does not make a difference.

      I have included the full catalina.out from the moment JSD begun its update and the full stack trace above in the following attachments:

      Workarounds

      • Restart JIRA. No errors occur after that.
      • When upgrading JIRA to 7.2.0, use a clean jira-home folder, without any add-ons.

        1. atlassian-jira.log
          1.62 MB
        2. catalina.out from the moment JSD started being updated.txt
          364 kB
        3. full stack trace.txt
          56 kB
        4. Screen Shot 2016-08-29 at 1.26.24 PM.png
          Screen Shot 2016-08-29 at 1.26.24 PM.png
          388 kB

              mwinsen Marty
              vfontes Vinicius Fontes
              Votes:
              26 Vote for this issue
              Watchers:
              52 Start watching this issue

                Created:
                Updated:
                Resolved: