Bug 1029494

Summary:	Document: Add warning not to copy HornetQ journal files among servers in cluster
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Miroslav Novak <mnovak>
Component:	Documentation	Assignee:	Nidhi <nsriniva>
Status:	CLOSED DUPLICATE	QA Contact:	Russell Dickenson <rdickens>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	mnovak, nsriniva, twells
Target Milestone:	---	Keywords:	Documentation, FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-04 10:35:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Miroslav Novak 2013-11-12 13:32:20 UTC

Description of problem:
If HornetQ journal is copied from one server to another and started then warning:

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. nodeID=630c8f17-3ee0-11e2-b591-cffd2592f65e

is printed to log. This is because HornetQ generates unique id during first start of server and is stored in journal. When this journal is copied to another server and configured to form (HornetQ) cluster with original server then there are two servers with the same id.

Comment 2 Miroslav Novak 2014-08-04 10:29:36 UTC

Hi Nidhi,

yes, this information is enough. This bz can be closed.

Thanks, 
Mirek

Comment 4 Nidhi 2014-08-04 10:37:30 UTC


*** This bug has been marked as a duplicate of bug 1089298 ***