> As has been discussed before, now that the System.exit calls are out of > 4.0.2, some packages can stop proper Tomcat shutdowns from happening. > Poolman (JDBC datasource pools and generic object pools) from > codestudio.com is one of these packages. For anyone that is interested, I > have made relatively minor changes to Poolman 2.1 beta source that support > a clean way of shutting poolman down under Tomcat 4.0.2 and allowing a > proper shutdown to occur. Vanilla Poolman relies on JVM shutdown hooks to > do resource cleanups, and of course these hooks no longer happen in Tomcat > 4.0.2 now that the System.exit calls are gone. So some Threads are left > running forever that used to be killed by the System.exit call. The new > source makes a new PoolMan.stop() method available that causes all pools to > close, the Lifeguard and Skimmer theads to end, and any JMX servers to > close. This can be invoked in the destroy() method of any appropriate > servlet. If anyone is interested in the changes, contact me by email.
Yes, I'd say that's the cleaest way to do it. Or write a lifecycle listener and associate it with the server (this looks even cleaner). Remy -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
