RE: JMX conflict in Tomcat 5.0
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 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. I also verified that the >jmxproxy part of the manager web-app also appears to be working. Assuming >that no other web-apps need JMX, is this an appropriate solution? Yeah, that should be fine. Thanks for testing ;) >Also, do web-apps located under /server/webapps have access to the >libraries >in /server/lib? This question isn't answered by the Classloader FAQ but I >seem to recall reading somewhere that they do have access to these >libraries. In that case, will Tomcat function properly with the JMX jars >in >server/lib? Not automatically, they have to be marked as privileged in the context declaration. But with this attribute set to true, the answer to the above is yes as well. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JMX conflict in Tomcat 5.0
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. I also verified that the jmxproxy part of the manager web-app also appears to be working. Assuming that no other web-apps need JMX, is this an appropriate solution? Also, do web-apps located under /server/webapps have access to the libraries in /server/lib? This question isn't answered by the Classloader FAQ but I seem to recall reading somewhere that they do have access to these libraries. In that case, will Tomcat function properly with the JMX jars in server/lib? Thanks, Mark -Original Message----- From: Mark Richards [mailto:[EMAIL PROTECTED] Sent: March 17, 2004 3:42 PM To: '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.CommunicationException: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is: java.io.InvalidClassException: javax.management.ObjectName; Local class not compatible: stream classdesc serialVersionUID=1081892073854801359 local class serialVersionUID=-5467795090068647408 java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is: java.io.InvalidClassException: javax.management.ObjectName; Local class not compatible: stream classdesc serialVersionUID=1081892073854801359 local class serialVersionUID=-5467795090068647408 java.io.InvalidClassException: javax.management.ObjectName; Local class not compatible: stream classdesc serialVersionUID=1081892073854801359 local class serialVersionUID=-5467795090068647408 at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteC all.java:240) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:117) at com.sun.jdmk.comm.RmiConnectorServerObjectImplV2_Stub.getAttribute(RmiConnec torServerObjectImplV2_Stub.java:316) at com.sun.jdmk.comm.RmiConnectorClient.connect(RmiConnectorClient.java:711) [snip] So, it would appear that Tomcat 5's JMX jar is overriding my web-app's JMX jar. Can anyone tell me how Tomcat 5 uses JMX? Is it possible to move Tomcat's JMX jar into the server/lib directory? I understand that Tomcat can use JMX for the management webapp, but is it required, or optional? Are there any other reasons to use JMX? The tomcat installation will be deployed stand-alone with only my web app and whatever comes standard with Tomcat 5 (i.e. the management web app, etc). Thanks, Mark -Original 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). 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. Tomcat uses modeler fairly heavily to build its beans, and modeler had an MX4J dependency last I checked. Yoav Shapira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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.CommunicationException: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is: java.io.InvalidClassException: javax.management.ObjectName; Local class not compatible: stream classdesc serialVersionUID=1081892073854801359 local class serialVersionUID=-5467795090068647408 java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is: java.io.InvalidClassException: javax.management.ObjectName; Local class not compatible: stream classdesc serialVersionUID=1081892073854801359 local class serialVersionUID=-5467795090068647408 java.io.InvalidClassException: javax.management.ObjectName; Local class not compatible: stream classdesc serialVersionUID=1081892073854801359 local class serialVersionUID=-5467795090068647408 at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteC all.java:240) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:117) at com.sun.jdmk.comm.RmiConnectorServerObjectImplV2_Stub.getAttribute(RmiConnec torServerObjectImplV2_Stub.java:316) at com.sun.jdmk.comm.RmiConnectorClient.connect(RmiConnectorClient.java:711) [snip] So, it would appear that Tomcat 5's JMX jar is overriding my web-app's JMX jar. Can anyone tell me how Tomcat 5 uses JMX? Is it possible to move Tomcat's JMX jar into the server/lib directory? I understand that Tomcat can use JMX for the management webapp, but is it required, or optional? Are there any other reasons to use JMX? The tomcat installation will be deployed stand-alone with only my web app and whatever comes standard with Tomcat 5 (i.e. the management web app, etc). Thanks, Mark -Original 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). 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. Tomcat uses modeler fairly heavily to build its beans, and modeler had an MX4J dependency last I checked. Yoav Shapira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JMX conflict in Tomcat 5.0
Hello, The jmx-remote.jar and jmx-remote-tools.jar were in the archive I downloaded from jakarta.apache.com (Tomcat 5.0.18). And I don't mean to imply that Tomcat doesn't work in general, I mean it doesn't work with my app (or, my app doesn't work with it - they don'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 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 them nor what their impact is. The jmx.jar is the Sun JMX 1.2.1 API and reference implementation (RI). >I should mention that if it is not possible to make Tomcat 5 work properly, It DOES work properly out of the box. In addition, it even works properly with the latest Sun RI. Older Sun or other implementations, I don't know. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JMX conflict in Tomcat 5.0
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. I should mention that if it is not possible to make Tomcat 5 work properly, downgrading to Tomcat 4.x is a solution we 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 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: JMX conflict in Tomcat 5.0 > >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 jars >our application appears to work but I was wondering what the ramifications >of this are for Tomcat. We are using the Sun implementation of JMX (I >think >it's version 1.1). > >Is there any way to make this work without mangling the Tomcat >installation? >Will Tomcat work properly with our JMX jars? > >Other details: >Our web-app conforms to Servlet 2.2 >JDK 1.3.1 >Changing our version of JMX to whatever Tomcat uses is not an option at >this >time. > >Thanks, > >Mark Richards >> >Software Developer >InSystems Corporation >Voice: (905) 513-1400 ext. 3552 >Fax: (905) 513-1419 ><mailto:[EMAIL PROTECTED]> >http://www.insystems.com > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JMX conflict in Tomcat 5.0
We originally put these jars there but it didn't work; our application was unable to connect to the MBean server (or listener... forgive me but JMX isn't my specialty). When we removed the Tomcat JMX jars and put ours in place, the app functioned as we expected. Thanks, Mark -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 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 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 jars our application appears to work but I was wondering what the ramifications of this are for Tomcat. We are using the Sun implementation of JMX (I think it's version 1.1). Is there any way to make this work without mangling the Tomcat installation? Will Tomcat work properly with our JMX jars? Other details: Our web-app conforms to Servlet 2.2 JDK 1.3.1 Changing our version of JMX to whatever Tomcat uses is not an option at this time. Thanks, Mark Richards >> Software Developer InSystems Corporation Voice: (905) 513-1400 ext. 3552 Fax: (905) 513-1419 <mailto:[EMAIL PROTECTED]> http://www.insystems.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JMX conflict in Tomcat 5.0
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 jars our application appears to work but I was wondering what the ramifications of this are for Tomcat. We are using the Sun implementation of JMX (I think it's version 1.1). Is there any way to make this work without mangling the Tomcat installation? Will Tomcat work properly with our JMX jars? Other details: Our web-app conforms to Servlet 2.2 JDK 1.3.1 Changing our version of JMX to whatever Tomcat uses is not an option at this time. Thanks, Mark Richards >> Software Developer InSystems Corporation Voice: (905) 513-1400 ext. 3552 Fax: (905) 513-1419 <mailto:[EMAIL PROTECTED]> http://www.insystems.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connection refused under hight load
AFAIK, this limit doesn't apply for TCP/IP connections, only netbios connections. Mark -Original Message- From: Cox, Charlie [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 08, 2001 8:17 AM To: '[EMAIL PROTECTED]' Subject: RE: Connection refused under hight load I know that NT4 Workstation only allows 10 concurrent network connections. I didn't think that limit had changed for Win2k Workstation. Even though your app is running on the same machine, it is still making tcpip requests which would count against the limit. This is to force people to buy NT Server. Charlie -Original Message- From: Markus Ebersberger [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 08, 2001 6:13 AM To: [EMAIL PROTECTED] Subject: Connection refused under hight load Hi, I'm testing a servlet-application that is using Tomcat v 3.1 (standalone, without Apache) running on Win2K Workstation. The tool I'm using for testing starts a (configurable) number of threads, each of which connects to the server, sends a HTTP-request and waits for the response. It runs on the same machine as the server. When I start many threads simultaneously, the server sometimes refuses connections (I get a ConnectException on client side). The tomcat logfile shows nothing unusual. Does someone know a possible reason for this behaviour or even a solution ? (I suspect that the "connection request queue" (I don't know the correct term ) of the operating system is too short, but where can i adjust this ?) Thanks in advance, Markus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
