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
# 5 sec
#modjk.updateInterval=5000
#modjk.user=
#modjk.pass=

# JMX with MX4J
mx.enabled=true
mx.httpPort=9050
mx.httpHost=localhost
#mx.jrmpPort=1099
#mx.jrmpHost=localhost

# Don't register request at
# JMX statistic (fix memory leak)
# see http://issues.apache.org/bugzilla/show_bug.cgi?id=28321
# (william barker comment)
request.registerRequests=false
==== end jk2.properties

Testet with Tomcat 5.0.25 MX4J 1.1.1.
You must install the mx4j-tools.jar $CATALINA-HOME//bin and add the jar to Tomcat System Classpath via $CATALINA-HOME/bin/setclasspath.bat
set CLASSPATH=%JAVA_HOME%\lib\tools.jar;%BASEDIR%\bin\mx4j-tools.jar


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)


-- This flat JMX configuration is a security risk...

Regards
Peter

Wilson Jimmy - jiwils schrieb:




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 manner? If so, can you show me a
sample client?



What I really want to do is update workers2.properties from a remote location. Basically, I have some JBoss/Tomcat servers clustered, and as one comes up/goes down, I would like to be able to programmatically update mod_jk2's workers and URI mappings. It seems like the Tomcat JK2 JMX proxies are the way to go about this. Is what I want to do even possible?

Jimmy





--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to