You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/08/05 13:48:27 UTC
DO NOT REPLY [Bug 22130] New: -
Tomcat VM not shutdown successfull as jk2 JMX handler is active
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
Summary: Tomcat VM not shutdown successfull as jk2 JMX handler is
active
Product: Tomcat 4
Version: 4.1.27
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Critical
Priority: Other
Component: Connector:Coyote JK 2
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: pr@webapp.de
I have configured at conf/jk2.properties (mx.port=9000). This starts
a mx4j Http and rmi JMX Apdator.
Tomcat Shutdown is not successful. All Tomcat Connector close but rmi and JMX
Handler are not close. The Vm not exists.
I analysed that org.apache.jk.common.JkMX destroy() method not stop the MX4J
Adaptors !
I see at start() this mserver.invoke(adaptor, "start", null,null) call.
Tested with 4.1.24, 4.1.27 and Tomcat 5 (5.0.3)
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org