When is contextDestroyed called?

java tomcat servletcontextlistener
OldCurmudgeon picture OldCurmudgeon · Jul 8, 2014 · Viewed 15.7k times · Source

Having implemented a ContextListener I can now happily deal with contextDestroyed events by closing down my connection pools and flushing my caches etc.

I was surprised recently when contextDestroyed was called at a time when my server was not being shut down - it seemed to be at some arbitrary time which I have not been able to track down.

Is there any defined event or set of circumstances that trigger contextDestroyed?

Should I ensure that everything I do when contextDestroyed is called is reversible? Do I need to make all my pools survive a destroyed/initialized cycle? Was I wrong to assume I would only get a contextDestroyed when Tomcat was being shut down or my war was being replaced?

Answer

glend picture glend · Jun 5, 2015

Through a series of trial and error testing I have found that contextDestroyed() is called when;

  1. The server is .WAR is being updated/removed.
  2. The server is shutdown due to administrator intervention.
  3. The server is shutdown due to a coding error. Something that would terminate a non-server application termination.

If you are experiencing issue #3, as you are suggesting, I think the best possible course of action is to safely (be sure not to create an infinite loop) call contextInitialized() to ensure pools are recreated properly.

Related questions

How to deploy a war file in Tomcat 7

I have copied the sample.war file into the webapps directory of Tomcat, and I can access localhost:8080. Now how will Tomcat deploy it, I mean do I need to open it in browser? How can I access the application?

Read More
Several ports (8005, 8080, 8009) required by Tomcat Server at localhost are already in use

I'm getting the following error when I try to run a simple JSP program on Tomcat in Eclipse. Several ports (8005, 8080, 8009) required by Tomcat v6.0 Server at localhost are already in use. The server may already be running in another process, …

Read More
Tomcat 404 error: The origin server did not find a current representation for the target resource or is not willing to disclose that one exists

I was following the tutorial on o7planning and got stuck at step 6: http://o7planning.org/en/10169/java-servlet-tutorial It's just a simple project that show HelloWorld but for some reason I keep getting 404 error. Detail: However the Tomcat welcome …

Read More