I don't know if you are aware of this ( it is somewhere in a commit message):
If you add a 'mx.port=9999' in jk2.properties, jk will try to load the http adapter of mx4j or jmxri. It will also expose all the jk handlers as mbeans ( in jk: domain ). You also need to copy mx4j-tools.jar in server/lib ( or lib/common for 3.3 ). This will give you a view of all the mbeans, including ability to change properties, etc. Pretty usefull if you want to get a top-level view of what's inside. In 3.3 you also need to add <MxInterceptor> to server.xml to expose the interceptors and contexts as mbeans. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
