[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question

[jbabad]

I'm labouring this one a bit more, I know... but having seen this in the server.log... I'm trying my luck...


  | 
  | 2009-02-13 10:45:14,913 DEBUG [org.jboss.messaging.core.impl.FailoverWaiter] (WorkerThread#6[192.168.8.125:47389]) org.jboss.messaging.core.impl.FailoverWaiter at 128b200 blocking on the failover lock, waiting for failover to start
  | 2009-02-13 10:45:15,750 DEBUG [org.jgroups.protocols.MERGE2] (Timer-4,192.168.8.117:7900) 192.168.8.117:7900 is looking for merge candidates, found initial_mbrs=[[own_addr=192.168.8.118:7900, coord_addr=192.168.8.117:7900, is_server=true], [own_addr=192.168.8.117:7900, coord_addr=192.168.8.117:7900, is_server=true]]
  | 2009-02-13 10:45:16,360 DEBUG [org.jgroups.protocols.MERGE2] (Timer-9,192.168.8.117:49704) 192.168.8.117:49704 is looking for merge candidates, found initial_mbrs=[[own_addr=192.168.8.118:56013, coord_addr=192.168.8.117:49704, is_server=true], [own_addr=192.168.8.117:49704, coord_addr=192.168.8.117:49704, is_server=true]]
  | 
Then later on....

  | 
  | 2009-02-13 10:46:14,914 DEBUG [org.jboss.messaging.core.impl.FailoverWaiter] (WorkerThread#6[192.168.8.125:47389]) org.jboss.messaging.core.impl.FailoverWaiter at 128b200 releasing the failover lock, checking again whether failover started ...
  | 2009-02-13 10:46:14,914 DEBUG [org.jboss.messaging.core.impl.FailoverWaiter] (WorkerThread#6[192.168.8.125:47389]) Timed out waiting for failover to start 
  | 2009-02-13 10:46:14,915 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] (WorkerThread#4[192.168.8.125:47391]) removing callback handler ServerInvokerCallbackHandler[5c4o83h-nlkeqt-fr4rzxwx-1-fr4sagqo-s2g+5c4o83h-nlkeqt-fr4rzxwx-1-fr4sagr5-s2l]
  | 2009-02-13 10:46:14,915 DEBUG [org.jboss.remoting.InvokerRegistry] (WorkerThread#4[192.168.8.125:47391]) removed SocketClientInvoker[11aed12, bisocket://192.168.8.125:342501498] from registry
  | 2009-02-13 10:46:14,917 DEBUG [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] (WorkerThread#4[192.168.8.125:47391]) SocketClientInvoker[11aed12, bisocket://192.168.8.125:342501498] disconnecting ...
  | 2009-02-13 10:46:14,919 DEBUG [org.jboss.jms.server.remoting.ServerSocketWrapper] (WorkerThread#4[192.168.8.125:47391]) wrote CLOSING byte

This has happened, but my client apps still continue to send/receive  messages after this. So I assume that it just picked up the same JMS connection and continued?

Thanks again.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209864#4209864

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209864