Hide Forgot
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.
Link: Added: This issue depends SOA-1310
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.
I'be assigned it to you for the QE bit, when you've got it done can you assign it darrin for documentation
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.
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?
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.
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.
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.
This issue is tentatively approved for SOA 4.3 CP03, pending results of engineering investigation.
Daniel is going to follow up on this one.
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.
Attachment: Added: remote-queue.jar
Attachment: Added: hajndi-queue.jar
Link: Added: This issue depends JBESB-3316
Link: Added: This issue relates to SOA-2125
This JIRA is superseded by SOA-2125 I'm going to close this JIRA.