RE: JMX conflict in Tomcat 5.0

2004-03-18 Thread Mark Richards
Thanks for the help! Mark -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: March 18, 2004 11:23 AM To: Tomcat Users List Subject: RE: JMX conflict in Tomcat 5.0 Hi, >I just wanted to provide another data-point on this issue in case anyone >has >any ide

RE: JMX conflict in Tomcat 5.0

2004-03-18 Thread Shapira, Yoav
Hi, >I just wanted to provide another data-point on this issue in case anyone >has >any ideas. >When I move the JMX jars from Tomcat's common/lib directory and put them >into the server/lib directory, my web-app works fine. Also, I tried >running >the manager and admin web-apps and they seem ok.

RE: JMX conflict in Tomcat 5.0

2004-03-18 Thread Mark Richards
o: 'Tomcat Users List' Subject: RE: JMX conflict in Tomcat 5.0 Ok, I tried with Tomcat 5.0.19 and 4.1.29. It works fine on 4.1.29 but it fails on 5.0.19 (and .18) with the following error: 2004-03-17 15:35:44,683 [DEBUG] (SystemSelectionAction.java:124) - com.sun.jdmk.comm.Co

RE: JMX conflict in Tomcat 5.0

2004-03-17 Thread Mark Richards
riginal Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: March 17, 2004 12:24 PM To: Tomcat Users List Subject: RE: JMX conflict in Tomcat 5.0 Hi, > The jmx-remote.jar and jmx-remote-tools.jar were in the archive I >downloaded from jakarta.apache.com (Tomcat 5.0.18). Perh

RE: JMX conflict in Tomcat 5.0

2004-03-17 Thread Shapira, Yoav
Hi, > The jmx-remote.jar and jmx-remote-tools.jar were in the archive I >downloaded from jakarta.apache.com (Tomcat 5.0.18). Perhaps it's worth trying with 5.0.19? Back to your original question: there's also commons-modeler (http://jakarta.apache.org/commons/modeler/) to consider. Tomca

RE: JMX conflict in Tomcat 5.0

2004-03-17 Thread Mark Richards
#x27;t work together, but both seem to work apart). Thanks, Mark -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: March 17, 2004 12:08 PM To: Tomcat Users List Subject: RE: JMX conflict in Tomcat 5.0 Hi, >We removed jmx-remote-tools.jar, jmx-remote.jar a

RE: JMX conflict in Tomcat 5.0

2004-03-17 Thread Shapira, Yoav
Hi, >We removed jmx-remote-tools.jar, jmx-remote.jar and jmx.jar from >TOMCAT_HOME/common/lib, and replaced these with the implementation of JMX >we >have been using on other platforms. jmx-remote.jar and jmx-remote-tools.jar are not part of the tomcat distribution. I don't know where you got t

RE: JMX conflict in Tomcat 5.0

2004-03-17 Thread Mark Richards
are willing to take, but we'd rather not. Thanks, Mark -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: March 17, 2004 11:00 AM To: Tomcat Users List Subject: RE: JMX conflict in Tomcat 5.0 Hi, You removed only the MX4J implementation, or other things as

RE: JMX conflict in Tomcat 5.0

2004-03-17 Thread Shapira, Yoav
Hi, You removed only the MX4J implementation, or other things as well? Yoav Shapira Millennium Research Informatics >-Original Message- >From: Mark Richards [mailto:[EMAIL PROTECTED] >Sent: Wednesday, March 17, 2004 10:55 AM >To: Tomcat Users List (E-mail) >Subject:

RE: JMX conflict in Tomcat 5.0

2004-03-17 Thread Mark Richards
--Original Message- From: D'Alessandro, Arthur [mailto:[EMAIL PROTECTED] Sent: March 17, 2004 10:57 AM To: Tomcat Users List Subject: RE: JMX conflict in Tomcat 5.0 Put these jars under your webapp/WEB-INF/lib folder... -Original Message- From: Mark Richards [mailto:[EMAIL P

RE: JMX conflict in Tomcat 5.0

2004-03-17 Thread D'Alessandro, Arthur
Put these jars under your webapp/WEB-INF/lib folder... -Original Message- From: Mark Richards [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 17, 2004 10:55 AM To: Tomcat Users List (E-mail) Subject: JMX conflict in Tomcat 5.0 Hello, I am working on a web-application that was

JMX conflict in Tomcat 5.0

2004-03-17 Thread Mark Richards
Hello, I am working on a web-application that was previously deployed on Websphere but we would like to deploy it on Tomcat 5.0. However, our application uses JMX and it seems that our JMX jars conflict with Tomcat's JMX jars. We found that if we replace Tomcat's JMX jars with our JMX jar