Call us: +1-415-738-4000
BigMemory is shut down through the Ehcache API. Note that Hibernate automatically shuts down its Ehcache
The recommended way to shutdown the Ehcache is:
Though not recommended, Ehcache also lets you register a JVM shutdown hook.
Ehcache provides a ServletContextListener that shuts down the CacheManager. Use this to shut down Ehcache automatically, when the web application is shut down. To receive notification events, this class must be configured in the deployment descriptor for the web application. To do so, add the following to web.xml in your web application:
<listener> <listener-class>net.sf.ehcache.constructs.web.ShutdownListener</listener-class> </listener>
The Ehcache CacheManager can optionally register a shutdown hook.
To do so, set the system property
This will shut down the CacheManager when it detects the Virtual Machine shutting down and
it is not already shut down.
Use the shutdown hook when the CacheManager is not already being shutdown by a framework you are using, or by your application.
Note: Shutdown hooks are inherently problematic. The JVM is shutting down, so sometimes things that can never be null are. Ehcache guards against as many of these as it can, but the shutdown hook should be the last option to use.
The shutdown hook is on CacheManager. It simply calls the shutdown method. The sequence of events is:
The shutdown hook runs when:
System.exit()is called, or the last non-daemon thread exits.
kill -SIGTERM pidor
kill -15 pidon Unix systems.
The shutdown hook will not run when:
kill -SIGKILL pidor
kill -9 pid.
TerminateProcesscall is sent to the process on Windows systems.
If Ehcache is shutdown dirty, all in-memory data will be retained if BigMemory is configured for restartability. For more information, refer to Fast Restartability.