Bug 779658 (SOA-2024) - JBm queue conflict in a cluster environment.
Summary: JBm queue conflict in a cluster environment.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2024
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation, JBoss Messaging
Version: 5.0.0 GA
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.2.0 GA
Assignee: David Le Sage
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-02 08:20 UTC by Marek Baluch
Modified: 2011-11-09 08:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-09 08:42:54 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2024 0 Blocker Closed JBm queue conflict in a cluster environment. 2012-11-19 14:39:33 UTC

Description Marek Baluch 2010-04-02 08:20:53 UTC 
Affects: Release Notes
Date of First Response: 2010-06-30 10:01:07
project_key: SOA

See linked issue.
Comment 1 Marek Baluch 2010-04-02 08:21:14 UTC 
Link: Added: This issue depends JBMESSAGING-1797
Comment 2 Marek Baluch 2010-06-02 07:36:55 UTC 
This error can be reproduced only when using a separate database for each cluster instance. If the database is shared between instances then everything seems OK.
Comment 3 Yong Hao Gao 2010-06-30 14:01:07 UTC 
Hi Marek,

JBoss Messaging cluster requires a shared DB to work properly. You can't use separate DB for each node.

Howard
Comment 4 Anne-Louise Tangring 2010-09-10 20:30:45 UTC 
Can we point to EAP documentation describing how it works?
This is not a bug, but we need to point users to the correct use cases. SOA 5.1.0
Comment 5 Anne-Louise Tangring 2010-09-10 20:30:45 UTC 
Affects: Added: [Release Notes]
Comment 7 Dana Mison 2011-01-05 00:14:27 UTC 
Writer: Added: dlesage
Comment 8 David Le Sage 2011-07-18 02:37:50 UTC 
Release Notes Docs Status: Added: Documented as Known Issue
Release Notes Text: Added: https://issues.jboss.org/browse/JBMESSAGING-1797

The user will encounter an org.jboss.messaging.util.ExceptionUtil if they use separate databases in a cluster. This is because the use of separate databases results in duplicated channel ids.  Always configure JBoss Message to use a shared database if clustering.  If you do so, you will not see this exception.
Comment 9 David Le Sage 2011-07-18 02:38:03 UTC 
Release note created.
Comment 10 Marek Baluch 2011-11-09 08:42:54 UTC 
Verified in release notest:
http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5/html-single/5.2.0_Release_Notes/index.html
Note You need to log in before you can comment on or make changes to this bug.