Bug 777718 (SOA-234)

Summary: Tracking issue: SOA-P with clustered JMS
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Martin Vecera <mvecera>
Component: JBossAS, EAPAssignee: Martin Vecera <mvecera>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 IR8   
Target Milestone: ---   
Target Release: 4.2 CR2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-234
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Full SOA-P
Last Closed: 2008-01-27 19:06:43 UTC Type: Task
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-12-14 10:57:37 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes
Date of First Response: 2008-01-23 13:53:46
project_key: SOA

This is intended as a tracking issue on how to run SOA-P with clustered JMS.

I was able to run clustered JMS and let the servers to share the messages.
And it really works out of the box (except for the ServerPeerID of course).

Steps to reproduce:
1. I switched off ServerInvoker's load balancing by setting the load balancer to FirstAvailable - just for sure.
2. I used jms-provider in the jboss-esb.xml of my service because plain JMS provider doesn't use ServiceInvoker and this means no load balancing on the ESB side.
3. I started 2 nodes and deployed the same service on both of them (it was not so easy - see SOA-231).
4. I sent some messages to the nodes and voila - the load balancing happend on the JMS side.

This means we can try to start failover testing now.
Comment 1 Martin Vecera 2007-12-14 10:57:53 UTC 
Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes]
Comment 2 Martin Vecera 2007-12-14 10:59:13 UTC 
Link: Added: This issue related SOA-231
Comment 3 Mark Little 2008-01-23 18:53:46 UTC 
Can we close this issue now?
Comment 4 Len DiMaggio 2008-01-23 19:54:21 UTC 
Closing this JIRA - as the JIRAs on which it is dependent are closed.