[jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1646) unable to restart live/backup pair after clean stop

Scott Clasen (JIRA) jira-events at lists.jboss.org
Wed Jun 10 13:24:56 EDT 2009


unable to restart live/backup pair after clean stop
---------------------------------------------------

                 Key: JBMESSAGING-1646
                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1646
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 2.0.0 Beta
         Environment: Standalone JBM 2.0-BETA servers on 2 RHEL 64 bit. JDK 1.6.0_13
            Reporter: Scott Clasen
            Assignee: Tim Fox


Unable to cleanly stop then restart a live/backup pair. I start the backup, start the live. Stop live with stop.sh, then backup with stop.sh.  Exception thrown on stopping the backup. Restart backup then live, another exception thrown in the backup.  Log snippets below.

Start Backup--->
 12:55:27,094 INFO [org.jboss.messaging.integration.bootstrap.JBMBootstrapServer]  Starting JBoss Messaging Server 
 12:55:32,536 INFO [org.jboss.messaging.core.server.impl.MessagingServerImpl]  Backup server will await live server before becoming operational 

Start Live-->
 12:55:53,243 INFO [org.jboss.messaging.integration.bootstrap.JBMBootstrapServer]  Starting JBoss Messaging Server 
 12:56:04,718 INFO [org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO journal selected 
 12:56:04,770 INFO [org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO loaded successfully 

Backup sees live -->
 12:56:09,169 INFO [org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO journal selected 
 12:56:09,221 INFO [org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO loaded successfully 
 12:56:10,778 INFO [org.jboss.messaging.core.server.impl.MessagingServerImpl]  Backup server is now operational 

Live up->
 12:56:11,233 INFO [org.jboss.messaging.core.server.impl.MessagingServerImpl]  JBoss Messaging Server version 2.0.0.BETA1 (tadpole, 102) started

Stop live--->
[sclasen at nydetemb01d /hboprod/itdept/dete/messaging-2.0.0.BETA1/bin]$ ./stop.sh 
[sclasen at nydetemb01d /hboprod/itdept/dete/messaging-2.0.0.BETA1/bin]$ 12:56:42,734 INFO [org.jboss.messaging.integration.bootstrap.JBMBootstrapServer]  Stopping JBoss Messaging Server 
12:56:44,719 INFO [org.jboss.messaging.core.server.impl.MessagingServerImpl]  JBoss Messaging Server version 2.0.0.BETA1 (tadpole, 102) stopped 

Stop Backup-->
[sclasen at nydetemb02d /hboprod/itdept/dete/messaging-2.0.0.BETA1/bin]$ ./stop.sh 
[sclasen at nydetemb02d /hboprod/itdept/dete/messaging-2.0.0.BETA1/bin]$ 15:58:16,092 INFO [org.jboss.messaging.integration.bootstrap.JBMBootstrapServer]  Stopping JBoss Messaging Server 
15:58:16,924 WARNING [org.jboss.kernel.plugins.dependency.StartStopLifecycleAction]  Error during stop for JMSServerManager 
java.lang.NullPointerException
	at org.jboss.messaging.core.server.impl.MessagingServerImpl.stop(MessagingServerImpl.java:309)
	at org.jboss.messaging.jms.server.impl.JMSServerManagerImpl.stop(JMSServerManagerImpl.java:172)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
	at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
	at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)
	at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)
	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)
	at org.jboss.kernel.plugins.dependency.LifecycleAction.uninstallActionInternal(LifecycleAction.java:249)
	at org.jboss.kernel.plugins.dependency.InstallsAwareAction.uninstallAction(InstallsAwareAction.java:157)
	at org.jboss.kernel.plugins.dependency.InstallsAwareAction.uninstallAction(InstallsAwareAction.java:42)
	at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleUninstallAction(SimpleControllerContextAction.java:79)
	at org.jboss.dependency.plugins.action.AccessControllerContextAction.uninstall(AccessControllerContextAction.java:131)
	at org.jboss.dependency.plugins.AbstractControllerContextActions.uninstall(AbstractControllerContextActions.java:58)
	at org.jboss.dependency.plugins.AbstractControllerContext.uninstall(AbstractControllerContext.java:354)
	at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:1631)
	at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1242)
	at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1146)
	at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:655)
	at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:568)
	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.undeployBean(AbstractKernelDeployer.java:394)
	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.undeployBeans(AbstractKernelDeployer.java:373)
	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.undeploy(AbstractKernelDeployer.java:162)
	at org.jboss.messaging.integration.bootstrap.JBMBootstrapServer.undeploy(JBMBootstrapServer.java:177)
	at org.jboss.messaging.integration.bootstrap.JBMBootstrapServer.shutDown(JBMBootstrapServer.java:256)
	at org.jboss.messaging.integration.bootstrap.JBMBootstrapServer$1.run(JBMBootstrapServer.java:105)
	at java.util.TimerThread.mainLoop(Timer.java:512)
	at java.util.TimerThread.run(Timer.java:462)

Restart Backup-->

15:58:32,350 INFO [org.jboss.messaging.integration.bootstrap.JBMBootstrapServer]  Starting JBoss Messaging Server 
15:58:34,221 INFO [org.jboss.messaging.core.server.impl.MessagingServerImpl]  Backup server will await live server before becoming operational 
15:58:34,273 INFO [org.jboss.messaging.core.server.impl.MessagingServerImpl]  JBoss Messaging Server version 2.0.0.BETA1 (tadpole, 102) started 

Restart Live-->
12:57:25,709 INFO [org.jboss.messaging.integration.bootstrap.JBMBootstrapServer]  Starting JBoss Messaging Server 
12:57:28,612 INFO [org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO journal selected 
12:57:28,612 INFO [org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO loaded successfully 


Backup sees Live-->
12:57:30,286 INFO [org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO journal selected 
12:57:30,286 INFO [org.jboss.messaging.core.persistence.impl.journal.JournalStorageManager]  AIO loaded successfully 
12:57:31,646 SEVERE [org.jboss.messaging.core.server.impl.MessagingServerPacketHandler]  Failed to initialise 
java.lang.IllegalStateException: Live and backup unique ids different. You're probably trying to restart a live backup pair after a crash
	at org.jboss.messaging.core.server.impl.MessagingServerImpl.initialiseBackup(MessagingServerImpl.java:611)
	at org.jboss.messaging.core.server.impl.MessagingServerPacketHandler.handlePacket(MessagingServerPacketHandler.java:99)
	at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.handlePacket(RemotingConnectionImpl.java:1562)
	at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.access$400(RemotingConnectionImpl.java:887)
	at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:488)
	at org.jboss.messaging.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:556)
	at org.jboss.messaging.integration.transports.netty.MessagingChannelHandler.messageReceived(MessagingChannelHandler.java:75)
	at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:105)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:567)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:803)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:387)
	at org.jboss.netty.handler.codec.frame.FrameDecoder.fireMessageReceived(FrameDecoder.java:284)
	at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:261)
	at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:184)
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:87)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:567)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:562)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:344)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:331)
	at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:303)
	at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:255)
	at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:176)
	at org.jboss.netty.util.internal.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:72)
	at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:49)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:619)







-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list