tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17892] - contextDestroyed not given time and finalizers not called on shutdown
Date Thu, 03 Mar 2005 23:11:43 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=17892>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=17892


markt@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From markt@apache.org  2005-03-04 00:11 -------
(In reply to comment #0)
> I have a contextDestroyed() method in a servlet.  It may take it up to a 
> couple of seconds to do its job.  Sometimes it completes, but more often the 
> web app is destroyed before it is done.
This shouldn't be in a servlet. It should be in a separate listener class. I
have a simple test case that takes 5s to execute contextDestroyed() and it
always completes.

> I also have a finalize method in a class for an asynchronous thread (not a 
> servlet).  The finalize never gets called.
There is no guarantee in Java when, or even if, a finalize() method will be called.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message