Hi, I face a similar problem. I am using JBoss 3.2.6 and make heavy use of (HA)JMS within a cluster. I have written a Scheduler Mbean using org.jboss.varia.scheduler.Schedulable. This mbean is deployed as cluster-singleton using the deploy-hasingleton directory. It works fine and after failing over to a new node it works fine again. But after the failover I get the the following warning every minute:
anonymous wrote : 2004-10-28 18:27:10,421 WARN [org.jboss.mq.Connection] Connection failure: | org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.) | at org.jboss.mq.Connection.asynchFailure(Connection.java:436) | at org.jboss.mq.Connection$PingTask.run(Connection.java:1385) | at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364) | at java.lang.Thread.run(Thread.java:534) | Caused by: java.io.IOException: ping timeout. | at org.jboss.mq.Connection$PingTask.run(Connection.java:1377) I have no idea, what it means (it is only a warning) , it happens only after failover even though everything works fine again. Is is a ping timeout to the dead node? Thanks in advance View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3853235#3853235 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3853235 ------------------------------------------------------- This Newsletter Sponsored by: Macrovision For reliable Linux application installations, use the industry's leading setup authoring tool, InstallShield X. Learn more and evaluate today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
