>>You have made a copy from mx4j.tools.jar to $catalina.hom/bin and
>>changed your setclasspath Skript ?
>>Please, send your log file output for more analyze steps.
While I was waiting on your response, I found out more information. My
catalina.out file contains information that indicates that
Hello Jimmy,
I have more then one Tomcat controlled with HTTP JMX Adaptor on my system.
Sorry, for the Typo.
You must changed the mx.httpPort=9000 .
This is the default MX4J HTTP Adpator Port.
You have made a copy from mx4j.tools.jar to $catalina.hom/bin and
changed your setclasspath Skript ?
Ple
>> the Remote JMX jk2 config is possible with this jk2.properties file
>>
>> With this configuration all JK2 Beans are reflect to the JMX MBeans
>> (Domain "apache").
>> Access the MBeans with http://localhost:9000. (Ignore the xsl mx4j error
>> at console)
Tomcat is definitely doing more with
Hello Jimmy,
the Remote JMX jk2 config is possible with this jk2.properties file
=== conf/jk2.properties
handler.list=modjk,mx
# Überschreibt den StandardPort des Channel-Sockets
channelSocket.port=8009
# Apache Status
modjk.webServerHost=localhost
modjk.webServerPort=80
modjk.statusPath=/jkstatus
>Furthermore, what are the interfaces of the JMX bean proxies that are
>mentioned? Are they "standard", "dynamic/model", or "open" mbeans? Is
>there a good page out there that details what the interfaces of the
>mentioned MBean proxies look like?
>Does anyone configure mod_jk2/jk2 in this mann
The mod_jk2/jk2 web page indicates that a JMX console can be utilized for
runtime configuration changes:
"On tomcat side, you must enable the JMX proxy. This is done by setting
"modjk.webServerHost" and "modjk.webServerPort" in jk2.properties to point
to the web server port that contains /jkstatus
