WARN [org.hornetq.core.cluster.impl.DiscoveryGroupImpl] (hornetq-discovery-group-thread-dg-group1) There are more than one servers on the network broadcasting the same node id.

[gorefest]

Hello,

I face the message

2012-07-04 12:23:37,769 WARN  [org.hornetq.core.cluster.impl.DiscoveryGroupImpl] (hornetq-discovery-group-thread-dg-group1) 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.

periodically in my server log. I run jboss 6.0 with a Gossip Router (windows HyperV Infrastructure with Linux VM does not do the trick ).

Although I define the node-Id in my start script plus the cluster group Id etc I am facing this message. Is there a known bug in jboss 6.0.0 Final ? Or does HornetQ do UDP Multicasting itself - from the Jboss point of view I know this is a problem in a windows world)?

I mounted a shared device, and both servers use it to define the queues etc., so I can see the behaviour of the queues as described. I also switched to NIO because it is a CIFS mountpoint, but with no success.

What am I doing wrong?

Thanks in advance,

marcus

PS: from the jgroups config I run the TCP stack,  which I attached as a standalone fragment

[ataylor]

have you copied the journals between the 2 servers

[gorefest]

Hi and thanks for Your reply

I switched the config to use a shared storage:

   <clustered>true</clustered>

   <shared-store>true</shared-store>

then I switched the conf to use NIO instead of AIO :

   <journal-type>NIO</journal-type>  

but : the nodes use the same journal directory (i thought that would be okay because i configured shared storage) :

   <journal-directory>/hornetq/journal</journal-directory>

does each cluster node need its own journal?

Thanks in advance,

marcus

[ataylor]

live and backups should share journals, if this is how you have it configured only 1 server should start, if both are starting then this is the problem. try using normal disc

[gorefest]

Hi,

thanks for the answer and sorry for my (vacation-) delay.

What does using normal disc mean?

Not sharing the journals?

I need a hot-failover so, I guess both servers have to run. What do I have to change on my config then?

Thanks in advance,

marucs

[ataylor]

I will re iterate, live and backups must point to the same journal, also make sure the backup is configured <backup>true</backup>. By using normal disc i mean not shared store, test your config on a single machine to make sure it works.

[gorefest]

Thanks for Your help!

I will try that.

Regards,

Marcus