JMS-JCA with BPMProcessor in SOA 5 throws JbpmException

[jlentz]

I created an ESB/jBPM integration project where BPMProcessor is used on the ESB side to start the jBPM process.  Initially, I was using a jms-provider on the ESB side, but had to change to the jms-jca-provider to support transactions. Using JMS-JCA with BPMProcessor on SOA 5, I get the following Exception:

org.jbpm.JbpmException: cannot mark externally managed transaction for rollback

            at org.jbpm.persistence.db.DbPersistenceService.endTransaction(DbPersistenceService.java:129)

There’s a Jira ticket (SOA-1881) related to this issue that has been resolved for SOA 4.3 CP04.  Can anyone tell me when this issue will be fixed for SOA 5?

Thanks,

Jennifer

[tkobayashi]

The fix has been already included in SOA-P 5.0.0.

https://jira.jboss.org/browse/SOA-1886

So, your issue may be different one.

Why don't you ask Red Hat support as you're using SOA-P?

Toshiya

[jlentz]

Thank you for your prompt reply Toshiya.  When testing with SOA 5 on 6/1 I received numerous "JbpmException: cannot mark externally managed transaction for rollback" messages in my log file.  I hadn't enabled all of my logging at this point, but since I'd seen this same message with my JBoss AS 5.1.0GA/JBoss ESB 4.7/JBPM 3.2.5 configuration, I thought that SOA-5 had the same problem.  After receiving your response this morning, I enabled all of my logging and reran my test on SOA 5 with a jms-jca provider and a BPMProcessor call.  It worked!!  I don't know why my 6/1 testing had such different results, but without the more detailed logging, any conclusions would be guesses.

Thanks again,

Jennifer