3 Replies Latest reply on Oct 31, 2013 5:15 AM by jeryma

    Unable to announce backup, retrying: java.lang.NullPointerException during failback

    pallavijain20
    pallavijain20 Feb 16, 2013 6:19 PM

      I have configured colocated live-backup hornetq server (hornetq-core-2.2.13) embedded in JBoss 7.1.1 two node cluster. Protocol used for clustering is tcp/TCPPING.

       

      My scenario is

       

      1. Jboss as with HQ in colocated live-backup  topology - Jboss01 live/ jboss02 backup & jboss02 live/ jboss01 backup

      2. start jboss 01 & jboss 02 both will announc backup

      3. stop jboss01 then jboss02 will failover and will start the backup server

      4. Start server jboss02 again and wait I get

      WARN  [org.hornetq.core.server.cluster.impl.ClusterConnectionImpl] (Thread-2 (HornetQ-server-HornetQServerImpl::serverUUID=9ec98bdb-7888-11e2-9727-005056bf0066-1759482265)) Unable to announce backup, retrying: java.lang.NullPointerException

              at org.hornetq.core.server.cluster.impl.ClusterConnectionImpl$2.run(ClusterConnectionImpl.java:485) [hornetq-core-2.2.13.Final.jar:]

              at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [hornetq-core-2.2.13.Final.jar:]

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]

              at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]

      5 shutdown jboss02 again Jboss01 will again failover correctly.

      6 Jboss02 will not failback untill unless journal directoires are cleared and both the servers are restarted sequntially.

       

      I saw similar jira entry for dedicated topology https://issues.jboss.org/browse/JBPAPP-7606

       

      Any suggestions