DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40534>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40534 Summary: JMX Monitoring in Tomcat Product: Tomcat 5 Version: Unknown Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Unknown AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] catalina.sh needs to have some type of environmental variable that allows the user to just pass the JMX options for remote monitoring on startup. The reason for this being is according to Sun's Documentation http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html if the port is already bound to when the JVM is started it throws an Exception and exists the JVM. So passing the JMX options via JAVA_OPTS or CATALINA_OPTS is setting it for both startup and shutdown. We only need this to be passed during startup. I can shutdown Tomcat ungracefully by using -force but that causes other 'issues' in a cluster environment during startup b/c the sessions weren't cleaned up properly. I can go manually tweak my catalina.sh script to support this but the minute I upgrade Tomcat I've broken it and I need to reapply my fix. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
