Broken build
timfox Nov 14, 2008 12:49 PMI've had a deeper look into way the build started failing recently/
Whilst it is true it was actually the randomfailovertest failing (Jeff was right), the reason for this seems to be the following in the logs:
(group:JBM-InVM-Transport-Threads-31601333):) Failed to delete consumer javax.management.InstanceNotFoundException: org.jboss.messaging:module=Core,type=Queue,address="FailoverTestAddress",name="FailoverTestAddress" at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:374) at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:527) at org.jboss.messaging.core.management.impl.ManagementServiceImpl.unregisterFromJMX(ManagementServiceImpl.java:360) at org.jboss.messaging.core.management.impl.ManagementServiceImpl.unregisterResource(ManagementServiceImpl.java:298) at org.jboss.messaging.core.management.impl.ManagementServiceImpl.unregisterQueue(ManagementServiceImpl.java:228) at org.jboss.messaging.core.postoffice.impl.PostOfficeImpl.removeBinding(PostOfficeImpl.java:239) at org.jboss.messaging.core.server.impl.ServerSessionImpl.doHandleDeleteQueue(ServerSessionImpl.java:580) at org.jboss.messaging.core.server.impl.ServerSessionImpl.handleDeleteQueue(ServerSessionImpl.java:555) at org.jboss.messaging.core.server.impl.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:127) at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.handlePacket(RemotingConnectionImpl.java:1306) at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.access$1(RemotingConnectionImpl.java:1242) at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:438) at org.jboss.messaging.core.remoting.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:322) at org.jboss.messaging.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:118) at org.jboss.messaging.util.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:105) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595)
This only started to occur (failing most test runs) after svn revision 5361, which contains the following change:
- ManagementService managementService = new ManagementServiceImpl(ManagementFactory.getPlatformMBeanServer(), false); + ManagementService managementService = new ManagementServiceImpl(ManagementFactory.getPlatformMBeanServer(), config.isJMXManagementEnabled());
So basically now jmx server is enabled by default, previously it wasn't. This would explain why we only see the error after the commit.
I have put a temporary hack in postoffficeImpl:removeBinding to get the suite to run ok, but this needs to be solved properly.
I suspect it's being called after the managementservice has shutdown.