Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-22032

Rendering user profile summary causes an exception with non-admin users when there are no projects in JIRA




      After a fresh 4.1.2 install with no projects added, going to the user profile summary tab for a normal user (in jira-users) causes an exception that is shown on the web UI. An example from the logs:

      2010-08-13 10:59:17,668 http-8080-2 ERROR testuser 659x276x1 1u9a8pf /secure/ViewProfile.jspa [velocity] Method getFragmentHtml threw exception for reference $activityStreamFrag in template templates/plugins/userprofile/summary-panel.vm at  [43,13]
      2010-08-13 10:59:17,669 http-8080-2 ERROR testuser 659x276x1 1u9a8pf /secure/ViewProfile.jspa [com.atlassian.velocity.DefaultVelocityManager] MethodInvocationException occurred getting message body from Velocity: com.atlassian.gadgets.GadgetParsingException: org.apache.shindig.gadgets.GadgetException: Unable to retrieve gadget xml. HTTP error 504
              at com.atlassian.gadgets.renderer.internal.GadgetSpecFactoryImpl.getGadgetSpec(GadgetSpecFactoryImpl.java:151)
              at com.atlassian.gadgets.renderer.internal.GadgetSpecFactoryImpl.getGadgetSpec(GadgetSpecFactoryImpl.java:68)
              at sun.reflect.GeneratedMethodAccessor166.invoke(Unknown Source)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:597)

      ... and so on.

      The summary screen renders normally when the user is in group jira-administrators even with no projects in the system.

      When even a single project is added to the system (seems there is no need even to add the user to the project) the summary tab renders correctly. When the project is removed, the error is back again.

      This is not a big issue since a real JIRA instance will necessarily have one or more projects in use, but in case this is reproduceable in other systems, it would be wise to have JIRA fail gracefully and show some kind of informative message so it wouldn't be necessary to start troubleshooting in the implementation phase.


        Issue Links



              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              f5b8a3a07e94 Väinö Ala-Härkönen
              13 Vote for this issue
              25 Start watching this issue