Hi, It's MX4J 1.1, not 2.x, and we have an enhancement item open for that.
Your assumption is correct, it's in the JMX jar in the /bin folder. However, that will be separated out as well, into the jmx.jar containing just the JMX API itself without an implementation, and an implementation jar. This separation, along with coding for JDK 1.5's JMX Remote, will be done in the tomcat 5.1 release branch I think. Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: Carl Olivier [mailto:[EMAIL PROTECTED] >Sent: Friday, June 18, 2004 9:26 AM >To: 'Tomcat Users List' >Subject: RE: Tomcat Stand-alone > >Hi. > >Does anyone know what version of mx4j is being shipped with TC 5.0.25? > >I assume it is the jmx.jar in the /bin folder? > >Regards, > >Calr > >-----Original Message----- >From: Shapira, Yoav [mailto:[EMAIL PROTECTED] >Sent: 18 June 2004 02:59 PM >To: Tomcat Users List >Subject: RE: Tomcat Stand-alone > > > >Hi, >The problem is not related to the one you saw, they just share the same >generic error. Please submit a Bugzilla item for this. > >Yoav Shapira >Millennium Research Informatics > > >>-----Original Message----- >>From: Carl Olivier [mailto:[EMAIL PROTECTED] >>Sent: Friday, June 18, 2004 7:55 AM >>To: '[EMAIL PROTECTED]' >>Subject: Tomcat Stand-alone >> >> >>Greetings again all. >> >>Having a very irritating problem. I am trying to run Tomcat 5.0.25 >>standalone using 3 HTTP1.1 Coyote connectors - one for "behind the >firwall >>access", one for standard HTTP requests to all hosts and contexts and 1 >for >>1 site running HTTPS (SSL) on a specific IP. >> >>Now, when the server starts all goes well up until near the end - where >the >>following error is thrown in the tomcat logs: >> >>2004/06/18 01:47:32 org.apache.coyote.tomcat5.MapperListener init >>WARNING: Error registering contexts >>java.util.ConcurrentModificationException >> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:782) >> at java.util.HashMap$EntryIterator.next(HashMap.java:824) >> at java.util.HashMap.putAllForCreate(HashMap.java:424) >> at java.util.HashMap.clone(HashMap.java:656) >> at >>mx4j.server.DefaultMBeanRepository.clone(DefaultMBeanRepository.java:5 6 >) >> at >>mx4j.server.MBeanServerImpl.findMBeansByPattern(MBeanServerImpl.java:1 6 >03) >> at >>mx4j.server.MBeanServerImpl.queryObjectNames(MBeanServerImpl.java:1568 ) >> at >>mx4j.server.MBeanServerImpl.queryMBeans(MBeanServerImpl.java:1512) >> at >>org.apache.coyote.tomcat5.MapperListener.init(MapperListener.java:115) >> at >>org.apache.coyote.tomcat5.CoyoteConnector.start(CoyoteConnector.java:1 5 >10) >> at >>org.apache.catalina.core.StandardService.start(StandardService.java:48 5 >) >> at >>org.apache.catalina.core.StandardServer.start(StandardServer.java:2298 ) >> at org.apache.catalina.startup.Catalina.start(Catalina.java:556) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j a >va:3 >>9 >>) >> at >>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess o >rImp >>l >>.java:25) >> at java.lang.reflect.Method.invoke(Method.java:324) >> at >org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:284) >> at >org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:422) >> >>After this, all 3 the HTTP1.1 Coyote connectors are paused. >> >>This clearly does not help matters. I read a bugzilla report about a >>similar problem in Tomcat 4.1.30 - being fixed, and was wondering if >this >>is >>related and would be fixed for TC 5? >>(http://issues.apache.org/bugzilla/show_bug.cgi?id=27315) >> >>The funny thing is have another server that is identically setup (same >>hardware, software, same TC, same sites/hosts/context) and this does >NOT >>happen there? >> >>Any assistance would be much appreciated! >> >>Regards, >> >>Carl Olivier >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] > > > > >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] 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]
