When JMX is enabled, in the jk2.properties file, and configured to use the MX4J JRMP interal adapter, a rmi registry is created and bound to the default port of 1099. If there is another application using that port and bind expection is thrown and the adaptor is never enabled.
A configuration option for the rmi registry port would sovle this problem. A setter for port does exist on the mx4j.tools.naming.NamingService object.
The lastest source for org.apache.jk.common.JkMX does not have this feature, and would be the place to incorporate it.
This is my first post to the mailing list and have been a long time user of Tomcat.
-Kevin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
