Details
Description
I have just tested the JBoss-Jetty module jboss-jetty-7.5.0.RC0.sar
and I see following errors in JBoss log files:
2011-08-17 15:05:57,466 WARN [org.eclipse.jetty.util.log] (main
EXCEPTION
java.lang.ClassNotFoundException: No ClassLoaders found for:
org.jboss.jetty.jmx.JettyMBean
at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:306)
at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:521)
at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at org.eclipse.jetty.util.Loader.loadClass(Loader.java:92)
at org.eclipse.jetty.jmx.ObjectMBean.mbeanFor(ObjectMBean.java:117)
at org.eclipse.jetty.jmx.MBeanContainer.addBean(MBeanContainer.java:243)
at org.eclipse.jetty.jmx.MBeanContainer.add(MBeanContainer.java:141)
at org.eclipse.jetty.util.component.Container.add(Container.java:204)
at org.eclipse.jetty.util.component.Container.update(Container.java:90)
at org.eclipse.jetty.server.Server.setThreadPool(Server.java:202)
at sun.reflect.GeneratedMethodAccessor177.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.set(XmlConfiguration.java:500)
at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:369)
at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:311)
at org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:273)
at org.jboss.jetty.Jetty.setXMLConfiguration(Jetty.java:150)
at org.jboss.jetty.Jetty.setConfigurationElement(Jetty.java:124)
at org.jboss.jetty.JettyService.createService(JettyService.java:258)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
Similar errors also reported for the classes:
org.eclipse.jetty.util.thread.jmx.QueuedThreadPoolMBean
org.eclipse.jetty.util.component.jmx.AbstractLifeCycleMBean
org.eclipse.jetty.server.nio.jmx.SelectChannelConnectorMBean
org.eclipse.jetty.server.nio.jmx.AbstractNIOConnectorMBean
org.eclipse.jetty.server.jmx.AbstractConnectorMBean
org.eclipse.jetty.http.jmx.HttpBuffersMBean
org.eclipse.jetty.util.component.jmx.AbstractLifeCycleMBean
org.eclipse.jetty.server.handler.jmx.HandlerCollectionMBean
org.eclipse.jetty.server.handler.jmx.AbstractHandlerContainerMBean
org.eclipse.jetty.server.handler.jmx.ContextHandlerCollectionMBean
org.eclipse.jetty.server.handler.jmx.HandlerCollectionMBean
org.eclipse.jetty.server.handler.jmx.AbstractHandlerContainerMBean
org.eclipse.jetty.server.handler.jmx.DefaultHandlerMBean
org.eclipse.jetty.server.handler.jmx.RequestLogHandlerMBean
org.eclipse.jetty.server.handler.jmx.HandlerWrapperMBean
org.eclipse.jetty.server.handler.jmx.AbstractHandlerContainerMBean
jetty-7.4.2.v20110526-jboss-4.2.3.GA-jsp-2.1.sar does not produce such errors.
Thank you for reporting this issue. It is similar to bug 332200, and is likely caused by the attempt to fix the latter. Since this issue pertains to Core Jetty it has been transferred to Eclipse bug 355001. It will be fixed in the final 7.5.0 release.