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=22130>. 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=22130 Tomcat VM not shutdown successfull as jk2 JMX handler is active ------- Additional Comments From [EMAIL PROTECTED] 2004-01-25 21:44 ------- The source of the problem is probably the RMI registry that is being created by the mx4j RMIAdapter. There is actually a non-daemon thread, the "RMI Reaper" thread: "RMI Reaper" prio=5 tid=0x8e89bd0 nid=0x8b4 waiting on monitor [0x9b1f000..0x9b1fdb8] at java.lang.Object.wait(Native Method) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118) at sun.rmi.transport.ObjectTable$Reaper.run(ObjectTable.java:279) at java.lang.Thread.run(Thread.java:479) The RMIAdapter should stop the NamingService, this should eliminate the deadlock. Btw: I got mx4j running with the following properties in jk.properties: mx.enabled=true mx.jrmpPort=1099 mx.jrmpHost=localhost Others mentioned mx.port=9000 which leads to total confusion. I used Tomcat 4.1.29 and mx4j 1.1.1. Anybody thinks to be in charge of this problem? Is there a release plan for 4.1.30? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
