3.1 bug? destroy() not called on a reload

[Jason Hunter <jh...@acm.org>]

Here's a note from my ISP regarding their testing of Tomcat 3.1.  If
it's true destroy() isn't called on a reload, that's a showstopper bug
in my opinion.  Could someone with more time check?

--
Stephan has done some early
testing of 3.1 and everything but class reloading seems to be stable.
There is a nasty bug in servlet class reloading that will probably
prevent us from enabling that on our 3.1 push. (The servlet.destroy
method is never called which is particularly bad if you have persistent
connections or threads fired up by your init method).
--

-jh-