Re: contextDestroyed() method not called

2016-03-19 Thread Daniel Savard
, - Daniel Savard 2016-03-16 23:56 GMT-04:00 Caldarale, Charles R <chuck.caldar...@unisys.com>: >> From: Daniel Savard [mailto:daniel.sav...@gmail.com] >> Subject: contextDestroyed() method not called > >> I noticed a problem with one of my web applications which re

RE: contextDestroyed() method not called

2016-03-19 Thread Caldarale, Charles R
> From: Daniel Savard [mailto:daniel.sav...@gmail.com] > Subject: Re: contextDestroyed() method not called Read the mailing list rules: don't top post. http://tomcat.apache.org/lists.html#tomcat-users > I'm running it on Window 2012 Server as well as Linux RHEL. Ok, good to know. &g

RE: contextDestroyed() method not called

2016-03-19 Thread Caldarale, Charles R
> From: Daniel Savard [mailto:daniel.sav...@gmail.com] > Subject: contextDestroyed() method not called > I noticed a problem with one of my web applications which requires > some cleanup when shutdown. It seems this cleanup isn't happening even > if everythi

Re: contextDestroyed() method not called

2016-03-19 Thread Daniel Savard
: >> From: Daniel Savard [mailto:daniel.sav...@gmail.com] >> Subject: Re: contextDestroyed() method not called > > Read the mailing list rules: don't top post. > http://tomcat.apache.org/lists.html#tomcat-users > >> I'm running it on Window 2012 Server as well as Linux RHEL.

contextDestroyed() method not called

2016-03-18 Thread Daniel Savard
and tested to see what is going on. It seems the contextDestroyed() method isn't called when stopping the web application or stopping the Tomcat instance. Here is my minimal code: package some.thing; import javax.servlet.ServletContextEvent; import javax.servlet.ServletContextListener; import

Re: contextDestroyed() method not called

2016-03-18 Thread Daniel Savard
Nevermind, the contextDestroyed() method is actually called as supposed and expected. The problem seems the logger is no longer able to output anything in the log file at this point even if I configured it to flush immediately the output. I replaced the log.info() statement by a System.out.println