brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aledsage <>
Subject [GitHub] brooklyn-server issue #376: deserializingClassRenames: handle renames in Con...
Date Tue, 11 Oct 2016 14:48:17 GMT
Github user aledsage commented on the issue:
    jenkins test failure is unrelated:
    2016-10-10 14:00:19,963 INFO  TESTNG FAILED: "Surefire test" - org.apache.brooklyn.feed.jmx.RebindJmxFeedTest.testJmxFeedIsPersisted()
finished in 185373 ms
    java.rmi.server.ExportException: Port already in use: 40123; nested exception is: Address already in use
    	at sun.rmi.transport.tcp.TCPTransport.listen(
    	at sun.rmi.transport.tcp.TCPTransport.exportObject(
    	at sun.rmi.transport.tcp.TCPEndpoint.exportObject(
    	at sun.rmi.transport.LiveRef.exportObject(
    	at sun.rmi.server.UnicastServerRef.exportObject(
    	at sun.rmi.registry.RegistryImpl.setup(
    	at sun.rmi.registry.RegistryImpl.<init>(
    	at java.rmi.registry.LocateRegistry.createRegistry(
    	at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(
    	at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(
    	at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(
    	at com.sun.jmx.mbeanserver.PerInterface.invoke(
    	at com.sun.jmx.mbeanserver.MBeanSupport.invoke(
    	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(
    	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(
    	at com.sun.proxy.$Proxy520.start(Unknown Source)
    	at org.apache.brooklyn.feed.jmx.RebindJmxFeedTest.runJmxFeedIsPersisted(
    	at org.apache.brooklyn.feed.jmx.RebindJmxFeedTest.testJmxFeedIsPersisted(
    Caused by: Address already in use
    	at Method)
    	at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(
    	at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(
    	at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(
    	at sun.rmi.transport.tcp.TCPTransport.listen(
    	... 57 more
    Unfortunately @ahgittin (cc @neykov) that means your 3-minute loop in `JmxService` constructor
(to retry the `namingServiceMBean.start()`) didn't fix the problem.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message