13 Replies Latest reply on Jan 24, 2012 2:59 AM by Andy Taylor

    More than one node with the same node id?

    Roberto Fabrizi Newbie

      I've been unsuccessfully trying to replicate the JMS Failover With Transaction Example, but I'm getting spammed with the error (on both servers):

      hornetq-discovery-group-thread-dg-group1] 15:25:32,116 WARNING [org.hornetq.core.cluster.impl.DiscoveryGroupImpl]  There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node. nodeID=91a0d2d2-7008-11e0-9a45-000347247807

      How can I get rid of it in a clustered, shared-store configuration?

       

      Here are the logs of the two standalone servers on two different machines.

      Live server:

      [main] 15:24:48,468 INFO [org.hornetq.integration.bootstrap.HornetQBootstrapServer]  Starting HornetQ Server

      [main] 15:24:52,692 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=true,journalDirectory=/backup/DB1ORAP8/hornetqSharedStore/data/journal,bindingsDirectory=/backup/DB1ORAP8/hornetqSharedStore/data/bindings,largeMessagesDirectory=/backup/DB1ORAP8/hornetqSharedStore/data/large-messages,pagingDirectory=/backup/DB1ORAP8/hornetqSharedStore/data/paging)

      [main] 15:24:52,692 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  Waiting to obtain live lock

      [main] 15:24:52,796 INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager]  Using AIO Journal

      [main] 15:24:52,900 WARNING [org.hornetq.core.server.impl.HornetQServerImpl]  Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this.

      [main] 15:24:53,524 INFO [org.hornetq.core.server.impl.AIOFileLockNodeManager]  Waiting to obtain live lock

      [main] 15:24:53,524 INFO [org.hornetq.core.server.impl.AIOFileLockNodeManager]  Live Server Obtained live lock

      [main] 15:24:57,276 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  trying to deploy queue jms.queue.exampleQueue

      [main] 15:24:57,952 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor]  Started Netty Acceptor version 3.2.3.Final-r${buildNumber} 10.170.35.14:5445 for CORE protocol

      [main] 15:24:58,056 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  Server is now live

      [main] 15:24:58,056 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  HornetQ Server version 2.2.2.Final (super-hornetq-fighter, 122) [91a0d2d2-7008-11e0-9a45-000347247807] started

      Backup server:

      [main] 16:38:22,504 INFO [org.hornetq.integration.bootstrap.HornetQBootstrapServer]  Starting HornetQ Server

      [main] 16:38:26,736 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  backup server is starting with configuration HornetQ Configuration (clustered=true,backup=true,sharedStore=true,journalDirectory=/backup/DB1ORAP8/hornetqSharedStore/data/journal,bindingsDirectory=/backup/DB1ORAP8/hornetqSharedStore/data/bindings,largeMessagesDirectory=/backup/DB1ORAP8/hornetqSharedStore/data/large-messages,pagingDirectory=/backup/DB1ORAP8/hornetqSharedStore/data/paging)

      [Thread-1] 16:38:26,736 INFO [org.hornetq.core.server.impl.AIOFileLockNodeManager]  Waiting to become backup node

      [Thread-1] 16:38:26,788 INFO [org.hornetq.core.server.impl.AIOFileLockNodeManager]  ** got backup lock

      [Thread-1] 16:38:26,944 INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager]  Using AIO Journal

      [Thread-1] 16:38:26,996 WARNING [org.hornetq.core.server.impl.HornetQServerImpl]  Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this.

      [Thread-1] 16:38:27,724 INFO [org.hornetq.core.server.cluster.impl.ClusterManagerImpl]  announcing backup

      [Thread-1] 16:38:27,724 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  HornetQ Backup Server version 2.2.2.Final (super-hornetq-fighter, 122) [91a0d2d2-7008-11e0-9a45-000347247807] started, waiting live to fail before it gets active

      [Thread-0 (group:HornetQ-server-threads23119024-18581191)] 16:38:28,244 INFO [org.hornetq.core.server.cluster.impl.ClusterManagerImpl]  backup announced

      [Thread-1] 16:38:32,612 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  trying to deploy queue jms.queue.exampleQueue

      [Thread-1] 16:38:32,872 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor]  Started Netty Acceptor version 3.2.3.Final-r${buildNumber} 10.170.35.204:5445 for CORE protocol

      [Thread-1] 16:38:33,028 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  Backup Server is now live

      [hornetq-discovery-group-thread-dg-group1] 16:38:33,964 WARNING [org.hornetq.core.cluster.impl.DiscoveryGroupImpl]  There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node. nodeID=91a0d2d2-7008-11e0-9a45-000347247807

       

      As always, thank you so much for the help.