• Bug
  • Status: Closed
  • Resolution: Fixed
  • drb
  • Reporter: sourceforgetracker
  • September 21, 2009
  • 0
  • Watchers: 0
  • September 22, 2009
  • September 22, 2009


It seems like the shutdown hook is not working properly in all situations.

Here is a use-case when it fails:

  • One distributed cache, using RMI
  • Two webapps deployed on the same Tomcat instance sharing the cache.

If the CacheManager instances are not explicitly shutdown before stopping the Tomcat instance, an exception is thrown (once for each webapp) and the Java process doesn’t finish.

Exception in thread “Multicast Server Thread” java.lang.NullPointerException at net.sf.ehcache.distribution.MulticastKeepaliveHeartbeatSender$MulticastServerThread.createCachePeersPayload(MulticastKeepaliveHeartbeatSender.java:138) at net.sf.ehcache.distribution.MulticastKeepaliveHeartbeatSender$MulticastServerThread.run(MulticastKeepaliveHeartbeatSender.java:107)

Attached is a minimal IDEA project for reproducing this (excluding the jar-files that didn’t fit).

Using: EhCache 1.2.1, Tomcat 5.5.15, Windows XP Sourceforge Ticket ID: 1521843 - Opened By: daniel_wiell - 13 Jul 2006 14:04 UTC


Fiona OShea 2009-09-22

Re-opening so that I can properly close out these issues and have correct Resolution status in Jira