Bug 778886 (SOA-1328)

Summary: Add support for HA-JNDI scenario when externalizing JMS instance with the jBPM enterprise configuration
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Taro Yasuma <tyasuma>
Component: Documentation, JBPM - within SOAAssignee: Kevin Conner <kevin.conner>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.3 CP01CC: dlesage, tkobayas
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1328
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-30 08:38:53 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:
Bug Depends On: 778868    
Bug Blocks:    
Attachments:
Description Flags
remote-queue.jar
none
hajndi-queue.jar none

Description Taro Yasuma 2009-05-26 07:55:33 UTC 
Date of First Response: 2009-06-03 10:04:29
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/297319
project_key: SOA

The customer is trying the jBPM enterprise configuration (JmsMessageServiceFactory, EntitySchedulerServiceFactory) 
on SOA-P4.3 and they understand that it's not fully supported yet and it depends on SOA-1310.

In the customer's use case, they'd like to have a SOA-P instance running jBPM and a separate EAP instance deploying 
all the JMS stuff and let JmsMessageServiceFactoryImpl look up a remote destination deployed on the separate instance 
but JmsMessageServiceFactoryImpl only looks up a local JNDI thus a JMS destination via InitialContext(), it's hardly to 
do for the remote lookup.

The customer is asking to support using HA-JNDI among the two(SOA-P and JMS) instances on the above use case in 
order to let the lookup work fine. 

In the summary,  their use case to be supported is having : 

1. the jBPM enterprise configuration(JmsMessageServiceFactory, EntitySchedulerServiceFactory) (SOA-1310),
2. a SOA-P instance running jBPM and a separate EAP(JMS) one,
3. HA-JNDI among the SOA and EAP instances and
4. access to remote JMS destination by JmsMessageServiceFactoryImpl.

If we support this use case, then the details of the configuration would be documented too.
Comment 1 Taro Yasuma 2009-05-26 07:56:09 UTC 
Link: Added: This issue depends SOA-1310
Comment 3 Martin Vecera 2009-06-03 14:04:29 UTC 
The solution will require some testing definitely. It is supposed to get into some configuration issues so this is not duable during a release cycle. My optimistic estimate (if everything goes well) is one week.
Comment 4 trev 2009-06-03 14:13:26 UTC 
I'be assigned it to you for the QE bit, when you've got it done can you assign it darrin for documentation
Comment 5 Martin Vecera 2009-06-03 14:30:26 UTC 
SOA-1310 must be fixed first, which will be in CP02. It is not possible to test this during a release cycle. So CP03 is the first possible Fix for.
Comment 6 Martin Vecera 2009-06-03 14:39:04 UTC 
The issue is not QE ready IMHO. I'd expect a how to document that we should test. We shouldn't be figuring out how to create the required configuration. Kevin, could you please have a look on it?
Comment 8 Taro Yasuma 2009-06-09 05:00:25 UTC 
What I(and the customer) expect on the JIRA is simple, i.e. enabling JmsMessageServiceImpl to look up the remote queue on a separate instance 
using HA-JNDI. JmsMessageServiceImpl which is responsible for sending Jobs as JMS messages to support asynchronous continuations,  is 
configured as 'message' service in jbpm.cfg.xml.
Comment 9 Taro Yasuma 2009-08-03 06:13:04 UTC 
My big concern is that if you use HA-JNDI among two nodes in the usecase, then the nodes are in the same cluster, I think. 
So they are heterogeneous products(SOA and EAP) each other (and possibly CPs in terms of EAP's version) in one cluster, 
but this heterogeneous configuration in cluster is never QEed I believe.
Comment 11 Burr Sutter 2009-12-23 15:11:49 UTC 
Related to Taro's concern, it does not make sense for us to test HA-JNDI between SOA-P and EAP instances.  If this is addressed it should be with two instances of SOA-P.
Comment 12 Anne-Louise Tangring 2010-02-25 18:46:27 UTC 
This issue is tentatively approved for SOA 4.3 CP03, pending results of engineering investigation.
Comment 13 Kevin Conner 2010-03-05 11:09:48 UTC 
Daniel is going to follow up on this one.
Comment 14 Daniel Bevenius 2010-03-10 12:35:53 UTC 
Kev and I have looked into this I'm attaching our findings.

For an example of configuring JBossESB to use a remote JMS destination see remote-queue.jar

For an example of configuring JBossESB to use HAJNDI to access a remote queue see hajndi-queue.jar.

The jars contain a readme.txt which describe the steps required to deploy and test these two configurations.
Comment 15 Daniel Bevenius 2010-03-10 12:37:09 UTC 
Attachment: Added: remote-queue.jar
Comment 16 Daniel Bevenius 2010-03-10 12:37:46 UTC 
Attachment: Added: hajndi-queue.jar
Comment 20 Kevin Conner 2010-05-13 15:03:55 UTC 
Link: Added: This issue depends JBESB-3316
Comment 21 Toshiya Kobayashi 2011-03-30 08:36:38 UTC 
Link: Added: This issue relates to SOA-2125
Comment 22 Toshiya Kobayashi 2011-03-30 08:37:30 UTC 
This JIRA is superseded by SOA-2125
I'm going to close this JIRA.