Re: [Mc4j-development] Tomcat -JMX
Brought to you by:
ghinkl
From: Slobodan V. <slo...@pr...> - 2004-12-23 15:53:04
|
I've succeeded (to expose Tomcat 5.5.x server for remote JMX management with j2se 1.4)! So if anybody is interested, Steps are the same as for Tomcat 5.0! ------------------------------------------------------------- To connect to Tomcat 5.0 you must currently enable the MX4J 1.1.1 proprietary connector. 1.. Edit jk2.properties and add the following: mx.port=1099 mx.enabled=true mx.httpPort=9051 mx.httpHost=localhost mx.jrmpPort=1099 mx.jrmpHost=localhost 2.. Download and copy the mx4j-tools and mx4j-jmx jars version 1.1.1 into the $CANTALINA_HOME/common/lib directory. 3.. Start tomcat looking for any exceptions. It will show an error message if it is unable to locate the MX4J libraries or if it cannot bind to the standard jndi port of 1099 or 9050. ---------------------------------------------------------------------------- ------ The only problem left is that, in Tomcat 5.5, JK doesn't have default property file (jk2.properties placed in conf directory for Tomcat 5.0) that gets loaded on 'init'. That is the reason why you HAVE to define 'propertiesFile' property for 'JkMain' class if you wan your configuration (from (e.g.) jk2.properties file) to get loaded. The easyest way to do this is to define additional property for 'AJP 1.3 Connector' defined in 'server.xml' file: Original Connector configuration: <!-- Define an AJP 1.3 Connector on port 8009 --> <Connector port="8009" enableLookups="false" redirectPort="8443" protocol="AJP/1.3" /> Adapted Connector configuration: <!-- Define an AJP 1.3 Connector on port 8009 --> <Connector port="8009" enableLookups="false" redirectPort="8443" protocol="AJP/1.3" propertiesFile="C:\jakarta-tomcat-5.5.4\conf\jk2.properties" /> That is all! Regards, Slobodan ----- Original Message ----- From: "Greg Hinkle" <gre...@gm...> To: <mc4...@li...> Sent: Wednesday, December 22, 2004 3:37 PM Subject: Re: [Mc4j-development] Tomcat -JMX > You should probably check with the tomcat user list, but I think I > recall the discussion being on the dev list that you could still > configure jkMX to utilize MX4J for remoting by setting up a > jk2.properties file as with versions prior to tomcat 5.5. I think they > just stopped shipping the default file. > > The instructions for setting up connections to tomcat < 5.5 on the > MC4J site should be applicable when using 5.5 with JDK 1.4 (though I > have not tried it myself). Let us know if you have any luck. > > > On Wed, 22 Dec 2004 10:40:01 +0100, Slobodan Vujasinovic > <slo...@pr...> wrote: > > Hi, > > > > Has anyone succeeded to expose Tomcat 5.5.x server for remote JMX management > > with j2se 1.4? > > > > I've done it with JRE 5.0 but I'm limited to j2se 1.4 use! > > > > Regards, > > Slobodan > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start reading now. > > http://productguide.itmanagersjournal.com/ > > _______________________________________________ > > Mc4j-development mailing list > > Mc4...@li... > > https://lists.sourceforge.net/lists/listinfo/mc4j-development > > > > > -- > Greg Hinkle > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Mc4j-development mailing list > Mc4...@li... > https://lists.sourceforge.net/lists/listinfo/mc4j-development > |