Bug 779960 (SOA-2320) - HornetQ clustering misconfiguration
Summary: HornetQ clustering misconfiguration
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2320
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Release Process
Version: 5.1.0.ER1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0 GA
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-15 11:28 UTC by Martin Vecera
Modified: 2011-10-04 14:50 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-04 14:50:16 UTC
Type: Bug

Attachments (Terms of Use)
server-SOA-2320.log.gz (19.82 KB, application/x-gzip)
2010-09-15 11:29 UTC, Martin Vecera 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2320 0 Major Closed HornetQ clustering misconfiguration 2013-07-29 14:14:14 UTC

Description Martin Vecera 2010-09-15 11:28:29 UTC 
project_key: SOA

SOA-P configured to use HornetQ constantly shows the following warning even if bound to localhost:
2010-09-15 13:20:21,764 WARN  [org.hornetq.core.cluster.impl.DiscoveryGroupImpl] (hornetq-discovery-group-thread-dg-group1) There are more than one servers on the network broa
dcasting 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 i
t 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.

Steps to reproduce:
1. unzip SOA-P
2. use HornetQ installer in jboss-as/extras
3. jboss-as/bin/run.sh -c production -b localhost

See the attached log file.
Comment 1 Martin Vecera 2010-09-15 11:29:33 UTC 
Attachment: Added: server-SOA-2320.log.gz
Comment 2 Miroslav Novak 2010-09-15 16:52:37 UTC 
We've tested this case and it seems that somebody has started EAP with HornetQ with the same configuration on the same network. Cluster will work even if you bind EAP server to localhost (-b localhost)
Comment 3 Martin Vecera 2010-12-21 15:21:03 UTC 
Link: Added: This issue is related to JBPAPP-5093
Comment 4 David Le Sage 2011-09-01 05:51:23 UTC 
Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage
Note You need to log in before you can comment on or make changes to this bug.