You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Shapira, Yoav" <Yo...@mpi.com> on 2004/08/27 18:58:12 UTC

Bugzilla http://issues.apache.org/bugzilla/show_bug.cgi?id=30762, servlet destroyed after contextDestroyed

Hi,
I've just verified
http://issues.apache.org/bugzilla/show_bug.cgi?id=30762 is indeed true:
the contextDestroyed gets fired before the servlet destroy method.  This
is a Spec violation.  The relevant code hasn't change since Tomcat
5.0.23, when changes were made to StandardContext#stop.  

I'm a bit surprised we haven't caught this by now, and the TCKs pass.
Am I testing wrong?  I attached a trivial WAR to the bugzilla issue that
anyone can use to reproduce this.

It seems like a simple fix. In StandardContext#stop (v1.130, on the
TOMCAT_5_0 branch), move listenerStop() from before to after the
children are stopped.  But even though it seems like a simple fix my
surprised at this basic bug prompted me to bring this item to the list's
attention.

Yoav Shapira
Millennium Research Informatics





This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged.  This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org