Look at http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18131. I might have been running into this problem , in addition to the KeelDirectServer hang, with Cocoon & Tomcat, looks like a mixture of issues with the OSWEGO concurrency 1.3.1 JAR which we have, and maybe even the Excalibur event package.
I think the context shutdown is a good thing to add regardless. Also, Steve was (I think) using the struts client when he saw the hung threads. But maybe just setDaemon() may be sufficient for KeelDirectServer.
Shash
This is true, KeelDirectServer is in a blocking receive in one of Doug Lea's concurrent classes. I tried marking the thread as a daemon using setDaemon(true), so in theory the finalizer thread should not wait for KeelDirectServer to exit. But there were other Fortress threads, using TPCThreadManager that were waiting around. I think the cleanest way would be to use the context shutdown hook, and then to call dispose on the container properly.
http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
