Hi Benson

There was a fix regarding JMX and Jetty [1] which was released with 4.2.8. 
Might give it a try.

[1] 
https://github.com/ops4j/org.ops4j.pax.web/commit/952d3728303444bd10d89c555db62b3bef608ba2


regards
Marc

Am Mittwoch, 31. August 2016 14:11:18 UTC+2 schrieb Benson Margulies:
>
> When we run a series of pax-exam tests of a Karaf application that uses 
> pax-web, we sooner or later start to get these backtraces. If we run any 
> single one of the integration tests by itself, we never see this.
>
> The karaf container is launched by a @ClassRule in a junit test, so this 
> can't easily be explained by Junit method parallelism starting more than 
> one.
>
> This does not abort the test, it just noises-up the log.
>
>
> 2016-08-31 08:05:05,203 | WARN  | pool-92-thread-1 | MBeanContainer       
>             | 56 - org.eclipse.jetty.util - 9.2.14.v20151106 | bean: 
> org.ops4j.pax.web.service.jetty.internal.JettyServerWrapper@1162445a
> javax.management.InstanceAlreadyExistsException: 
> org.ops4j.pax.web.service.jetty.internal:type=jettyserverwrapper,id=0
> at 
> com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)[:1.8.0_60]
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)[:1.8.0_60]
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)[:1.8.0_60]
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)[:1.8.0_60]
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)[:1.8.0_60]
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)[:1.8.0_60]
> at 
> org.eclipse.jetty.jmx.MBeanContainer.beanAdded(MBeanContainer.java:209)[48:org.eclipse.jetty.jmx:9.2.14.v20151106]
> at 
> org.eclipse.jetty.jmx.MBeanContainer.beanAdded(MBeanContainer.java:142)[48:org.eclipse.jetty.jmx:9.2.14.v20151106]
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.addEventListener(ContainerLifeCycle.java:367)[56:org.eclipse.jetty.util:9.2.14.v20151106]
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.addBean(ContainerLifeCycle.java:257)[56:org.eclipse.jetty.util:9.2.14.v20151106]
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.addBean(ContainerLifeCycle.java:231)[56:org.eclipse.jetty.util:9.2.14.v20151106]
> at 
> org.ops4j.pax.web.service.jetty.internal.JettyServerImpl.start(JettyServerImpl.java:164)[69:org.ops4j.pax.web.pax-web-jetty:4.2.4]
> at 
> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Stopped.start(ServerControllerImpl.java:415)[69:org.ops4j.pax.web.pax-web-jetty:4.2.4]
> at 
> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.start(ServerControllerImpl.java:71)[69:org.ops4j.pax.web.pax-web-jetty:4.2.4]
> at 
> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Unconfigured.configure(ServerControllerImpl.java:700)[69:org.ops4j.pax.web.pax-web-jetty:4.2.4]
> at 
> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.configure(ServerControllerImpl.java:87)[69:org.ops4j.pax.web.pax-web-jetty:4.2.4]
> at 
> org.ops4j.pax.web.service.internal.Activator.updateController(Activator.java:351)[70:org.ops4j.pax.web.pax-web-runtime:4.2.4]
> at 
> org.ops4j.pax.web.service.internal.Activator$3.run(Activator.java:293)[70:org.ops4j.pax.web.pax-web-runtime:4.2.4]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_60]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_60]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_60]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_60]
>

-- 
-- 
------------------
OPS4J - http://www.ops4j.org - [email protected]

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to