Bug 777608 (SOA-117)

Summary: Clustering cannot work out-of-box
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Martin Vecera <mvecera>
Component: JBoss MessagingAssignee: Len DiMaggio <ldimaggi>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecified   
Target Milestone: ---   
Target Release: 4.2 IR5   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-117
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-12 15:08:50 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 Martin Vecera 2007-11-09 14:23:35 UTC 
Date of First Response: 2007-11-09 10:59:43
project_key: SOA

This issue is meant as a blocker for other issues related to clustering.

Clustering configuration can't ever work out-of-box!
Because:
1) JBM cannot run in a cluster with HSQLDB
2) You have to set different ServerPeerID in JBM config on each node to make it work.

It is not working in EAP either.
Maybe we can close this issue immediately, I just wanted to raise my voice for us to take it into account.

And are we going to support clustering in soa-standalone?
Comment 1 Martin Vecera 2007-11-09 14:28:24 UTC 
We need to solve JBAPP-413 before solving this issue.
Comment 2 Martin Vecera 2007-11-09 14:28:24 UTC 
Link: Added: This issue is related to JBPAPP-413
Comment 3 Tim Fox 2007-11-09 15:59:43 UTC 
JBM can't use HSQL for clustering because 

a) It requires a shared database viewable by all nodes
b) HSQLDB does not have any transaction isolation, and is generally crappy

The user will have to specify a different datasource e.g. point it to a mysql database, and make sure each node has a unique server id to get this to work from the out of the box config.

Note that, the out of the box config will *still start up* without making any changes, you won't get any errors, it's just that if you start other nodes you clustering of queues and topics won't work properly.

But please bear in mind, this is nothing new.

JBoss MQ doesn't work out of the box in clustered config either! JBM is no different. Both JBoss MQ and JBoss Messaging require a shared database to work. So there always has been and always will be an extra step needed to get either JBoss MQ or JBM to work properly in a clustered config.

Nothing to see here.. move along.
Comment 4 Len DiMaggio 2007-11-09 18:16:14 UTC 
Link: Added: This issue is related to JBESB-1316
Comment 5 Len DiMaggio 2007-11-09 18:18:00 UTC 
Link: Added: This issue related SOA-84
Comment 6 Mark Little 2007-11-12 13:49:33 UTC 
Can we close this now?
Comment 7 Len DiMaggio 2007-11-12 18:52:47 UTC 
Link: Added: This issue related SOA-135
Comment 8 Len DiMaggio 2007-11-26 20:29:30 UTC 
Link: Removed: This issue related SOA-84