HAJMS failover takes about 3 minutes

[sheckler]

HAJMS failover (JBoss 3.2.5) takes about 3 minutes with many exceptions
logged several times like

[org.jboss.mq.Connection] Connection failure:
[org.jboss.ejb.plugins.jms.JMSContainerInvoker] JMS provider failure detected:
[org.jboss.ejb.plugins.jms.JMSContainerInvoker] Trying to reconnect to JMS provider
[org.jboss.ejb.plugins.jms.JMSContainerInvoker] Could not stop JMS connection
org.jboss.mq.SpyJMSException: Cannot disable the connection with the JMS server; - nested throwable: (java.io.IOException: Client is not connected))
2004-10-21 20:30:13,343 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnected to JMS provider
2004-10-21 20:30:13,375 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] JMS provider failure detected:
javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory

[org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnected to JMS provider

At the end the web-console shows the new master.

Is this throwing of many exceptions for about 3 minutes normal behaviour or could there be some misconfiguration?
Can I speed up the failover by configuration?

Thanks in advance

Stefan Heckler
PSI AG, Germany

[adrian.brock]

This was fixed in 3.2.6

It was a bug in the jboss clustering hasingleton that meant it had to wait for a
clustered method invocation to timeout before it detected the original server had failed.

Please, please, please - test the latest and greatest before posting in future.

[sheckler]

I did test the latest:

http://www.jboss.org/index.html?module=bb&op=viewtopic&t=55430

[nitin888]

hi,

I'm getting a similar error. I thought there's a bug in 3.2.5 & upgraded to 3.2.6, but still getting these messages.
Have I done something wrong??

If you need anymore info please let me know.

thanks in advance,
Nitin.







2004-10-28 08:42:04,327 WARN [org.jboss.mq.Connection] Connection failure:
org.jboss.mq.SpyJMSException: Exiting on IOE; - nested throwable: (java.io.EOFException)
at org.jboss.mq.Connection.asynchFailure(Connection.java:436)
at org.jboss.mq.il.uil2.UILClientILService.asynchFailure(UILClientILService.java:145)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleStop(SocketManager.java:402)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:334)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2603)
at java.io.ObjectInputStream.readByte(ObjectInputStream.java:845)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:281)
... 1 more
2004-10-28 08:42:04,327 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] JMS provider failure detected:
org.jboss.mq.SpyJMSException: Exiting on IOE; - nested throwable: (java.io.EOFException)
at org.jboss.mq.Connection.asynchFailure(Connection.java:436)
at org.jboss.mq.il.uil2.UILClientILService.asynchFailure(UILClientILService.java:145)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleStop(SocketManager.java:402)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:334)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2603)
at java.io.ObjectInputStream.readByte(ObjectInputStream.java:845)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:281)
... 1 more
2004-10-28 08:42:04,343 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Trying to reconnect to JMS provider
2004-10-28 08:42:14,343 ERROR [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Could not stop JMS connection
org.jboss.mq.SpyJMSException: Cannot disable the connection with the JMS server; - nested throwable: (java.io.IOException: Client is not connected)
at org.jboss.mq.Connection.doStop(Connection.java:1289)
at org.jboss.mq.Connection.stop(Connection.java:718)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStop(JMSContainerInvoker.java:832)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.onException(JMSContainerInvoker.java:1265)
at org.jboss.mq.Connection.asynchFailure(Connection.java:446)
at org.jboss.mq.il.uil2.UILClientILService.asynchFailure(UILClientILService.java:145)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleStop(SocketManager.java:402)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:334)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.IOException: Client is not connected
at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:229)
at org.jboss.mq.il.uil2.SocketManager.sendMessage(SocketManager.java:197)
at org.jboss.mq.il.uil2.UILServerIL.setEnabled(UILServerIL.java:189)
at org.jboss.mq.Connection.doStop(Connection.java:1285)
... 8 more
2004-10-28 08:42:14,530 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnected to JMS provider

[sheckler]

Thanks for answering. With 3.2.6 the failover is working fine, but dependent from the number of MDB's it also can take quite a long time.

Unfortunately I still have this warning after failing over: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=47458

Maybe You have an explanation for this behaviour.

Thanks
Stefan