InvocationTargetException when Accessing Monitoring URL on JIRA

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install jira-javamelody-1.48.0.jar on JIRA v6.0.8

What is the expected output? What do you see instead?

Expect Javamelody to be accessible on /monitoring URL.

Instead, get Exception.  From JIRA log:

2013-11-26 18:25:44,163 http-bio-8080-exec-14 ERROR      [500ErrorPage.jsp] 
Exception caught in 500 page java.lang.reflect.InvocationTargetException
java.lang.IllegalStateException: java.lang.reflect.InvocationTargetException
    at net.bull.javamelody.JiraMonitoringFilter.getUser(JiraMonitoringFilter.java:292)
    at net.bull.javamelody.JiraMonitoringFilter.checkJiraAdminPermission(JiraMonitoringFilter.java:109)
    at net.bull.javamelody.JiraMonitoringFilter.hasNotPermission(JiraMonitoringFilter.java:100)
    at net.bull.javamelody.JiraMonitoringFilter.doFilter(JiraMonitoringFilter.java:90)
    at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter.doFilter(DelegatingPluginFilter.java:74)  <+36> (IteratingFilterChain.java:42) (ServletFilterModuleContainerFilter.java:77) (ServletFilterModuleContainerFilter.java:63) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (ChainedFilterStepRunner.java:84) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (AbstractCachingFilter.java:33) (AbstractHttpFilter.java:31) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (AbstractEncodingFilter.java:41) (AbstractHttpFilter.java:31) (PathMatchingEncodingFilter.java:49) (AbstractHttpFilter.java:31) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (JiraStartupChecklistFilter.java:74) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (ChainedFilterStepRunner.java:84) (JiraFirstFilter.java:57) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (StandardWrapperValve.java:225) (StandardContextValve.java:123) (AuthenticatorBase.java:472) (StandardHostValve.java:168) (ErrorReportValve.java:98) (StandardEngineValve.java:118) (AccessLogValve.java:927) (CoyoteAdapter.java:407) (AbstractHttp11Processor.java:1001) (AbstractProtocol.java:585) (JIoEndpoint.java:310)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:724)
Caused by: java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at net.bull.javamelody.JiraMonitoringFilter.getUser(JiraMonitoringFilter.java:285)
Caused by: java.lang.NullPointerException
    at com.atlassian.spring.container.ContainerManager.getComponent(ContainerManager.java:33)
    ... 48 more

What version of the product are you using? On what application server, JDK, 
operating system?

JavaMelody: v1.48.0
JIRA: 6.0.8
Tomcat/7.0.29
Java: JDK 1.7.0_40
OS: Linux 2.6.18-194.26.1.el5

Please provide any additional information below.

1) Was previously running v1.47.0.  Upgraded by shutting down JIRA, manually 
upgrading the jar, and then restarting

2) Was able to roll back to v1.47.0 with no problems.

Original issue reported on code.google.com by msymo...@gmail.com on 26 Nov 2013 at 7:55

[GoogleCodeExporter]

This is an unfortunate regression of v1.48 in JIRA, caused by the fix of issue 
359 for Confluence 5.3.
This should be fixed in trunk by revision 3585 (not yet tested).

I have made a new build of the plugin from the trunk and it is available:
https://javamelody.googlecode.com/files/jira-javamelody-20131129.jar

Original comment by evernat@free.fr on 29 Nov 2013 at 4:55

[GoogleCodeExporter]

Tested OK with JIRA 6.0.4

Original comment by evernat@free.fr on 30 Nov 2013 at 8:35

• Changed state: Fixed

[GoogleCodeExporter]

I'll test on Monday 2nd Dec.

Original comment by msymo...@gmail.com on 30 Nov 2013 at 10:39

[GoogleCodeExporter]

Tested JavaMelody v1.48.1 with both:

JIRA v6.0.8 and
Confluence v5.3.1

...and all looks good.

Original comment by msymo...@gmail.com on 2 Dec 2013 at 8:23