lemonzone2010 / javamelody

Automatically exported from code.google.com/p/javamelody
0 stars 0 forks source link

JavaMelody Causes JIRA to not Shutdown: "exception while checking sessions" #397

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Stop JIRA Service
2. Examine JIRA log atlassian-jira.log

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

Expected behaviour is that JIRA should shut down cleanly.  What is happening 
instead is that JIRA is not shutting down and the process has to be killed 
manually.  The log contains an exception:

{{{
2014-03-29 13:51:04,704 localhost-startStop-2 INFO      
[atlassian.jira.startup.DefaultJiraLauncher] Stopping launchers
2014-03-29 13:51:04,880 localhost-startStop-2 INFO      
[atlassian.plugin.manager.DefaultPluginManager] Shutting down the plugin system
2014-03-29 13:51:14,263 javamelody WARN anonymous 1096x1x1 - xxx.xxx.xxx.xxx / 
[net.bull.javamelody] exception while checking sessions
java.lang.NullPointerException
    at java.util.concurrent.ConcurrentHashMap.hash(ConcurrentHashMap.java:333)
    at java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1175)
    at net.bull.javamelody.SessionListener.sessionDestroyed(SessionListener.java:313)
    at net.bull.javamelody.SessionListener.unregisterSessionIfNeeded(SessionListener.java:365)
    at net.bull.javamelody.SessionListener.unregisterInvalidatedSessions(SessionListener.java:374)
    at net.bull.javamelody.PluginMonitoringFilter.unregisterInvalidatedSessions(PluginMonitoringFilter.java:106)
    at net.bull.javamelody.PluginMonitoringFilter$1.run(PluginMonitoringFilter.java:52)
    at java.util.TimerThread.mainLoop(Timer.java:555)
    at java.util.TimerThread.run(Timer.java:505)
}}}

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

JavaMelody 1.50.0 (although logs show that issue has existed since 1.45.0)
JIRA 5.22 - 6.17
Java JDK  1.7.0_51
Linux OS

Please provide any additional information below.

Original issue reported on code.google.com by msymo...@gmail.com on 29 Mar 2014 at 4:09

GoogleCodeExporter commented 9 years ago
I have seen this exception too.
I have fixed it in trunk (revision 3759) and it's ready for the next release 
(1.51).

A new build is attached. Can you confirm that it fixes the exception?
(I am not sure if that is the cause or not for JIRA to not shutdown)

Original comment by evernat@free.fr on 31 Mar 2014 at 1:15

Attachments:

GoogleCodeExporter commented 9 years ago
Sorry that I missed your comment for 3 days.  I'll only be able to test the new 
build on 5th April, at the earliest.

I know of a couple of other plugins that seem to give problems when during JIRA 
- but stopping them in UPM first and then shutting down JIRA whilst JavaMelody 
is still running should give a good test. 

Original comment by msymo...@gmail.com on 3 Apr 2014 at 11:59

GoogleCodeExporter commented 9 years ago
Tested jira-javamelody-20140331.jar.

Exception no longer seems to occur. 

Original comment by msymo...@gmail.com on 5 Apr 2014 at 2:52

GoogleCodeExporter commented 9 years ago
ok, thanks

Original comment by evernat@free.fr on 6 Apr 2014 at 2:07