Bug 777718 (SOA-234) - Tracking issue: SOA-P with clustered JMS
Summary: Tracking issue: SOA-P with clustered JMS
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-234
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossAS, EAP
Version: 4.2 IR8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CR2
Assignee: Martin Vecera
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-14 10:57 UTC by Martin Vecera
Modified: 2008-01-27 19:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Full SOA-P
Last Closed: 2008-01-27 19:06:43 UTC
Type: Task

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 777715 0 high CLOSED Cannot deploy a service to a cluster node 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-234 0 None None None Never

Internal Links: 777715

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.
Note You need to log in before you can comment on or make changes to this bug.