> -----Original Message----- > From: Christopher Schultz [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 14, 2007 12:34 PM > To: Tomcat Users List > Subject: Re: Listener Shutdown Order? > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Jim, > > Jim Garrison wrote: > >> From: Christopher Schultz [mailto:[EMAIL PROTECTED] > >> > >> "Notification that the servlet context is *about* to be shut down. All > >> servlets and filters have been destroy()ed before any > >> ServletContextListeners are notified of context destruction." > > > > What I'm seeing is that servlet destroy() is being called AFTER the > > listeners have been shutdown. If I'm reading the quote above right, > > this shouldn't happen; servlets should have already been destroy()ed > > before the listener is shutdown. > > > I checked the Tomcat 5.5 source, and this is what happens in > StandardContext.stop(): > > . > . > .
You are, of course, correct and there is no bug. I was getting confused due to multiple contexts running in a single server. I've sorted everything out now and it all appears to work as expected. The root cause of my confusion was a bug in the Eclipse debugger's variable-value tooltip display, which can display the wrong value if there are two instances of a Class loaded under different classloaders. IMPORTANT NOTICE: This message may contain confidential information. If you have received this e-mail in error, do not use, copy or distribute it. Do not open any attachments. Delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
