DO NOT REPLY [Bug 4033] - JamesSpoolManager doesn't shutdown gracefully

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4033>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4033

JamesSpoolManager doesn't shutdown gracefully





------- Additional Comments From farsight@alum.mit.edu  2002-10-06 22:20 -------
The POP3 (and the other protocol services) shutdown problems are not quite the 
same as the SpoolManager.  Those problems are due to some issues in the 
ConnectionManager being used.  ConnectionManager changes in my proposal later 
today (ran a little bit late with this one) should resolve that issue once and 
for all.

The SpoolManager code now implements dispose(), and calls destroy() for each 
of the mailets.  But it has a more serious problem than can be disastrous.  
Specifically, there is a potential race condition in the SpoolManager between 
the worker threads that actually process the mail and the action of the dispose
() method, which destroys the mailets.  That's bad.

Not sure how critical this issue is, as it only affects systems using mailets 
with non-trivial destroy() methods.  And it only manifests itself on shutdown 
and, even then, only some of the time.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>