[
http://jira.jboss.com/jira/browse/JBESB-1438?page=comments#action_12397073 ]
Daniel Bevenius commented on JBESB-1438:
----------------------------------------
Thanks, Kevin. I'm trying to verify this at the moment but not being able to since my
last svn update.
I'm getting the following error when I deploy the quickstart (the one attached):
Caused by: org.jboss.soa.esb.actions.ActionLifecycleException: Attribute 'command'
has an invalid value- see CommandVehicle.Operation enum for possible values
at
org.jboss.soa.esb.services.jbpm.actions.BpmProcessor.initialise(BpmProcessor.java:61)
at
org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.initialise(OverriddenActionLifecycleProcessor.java:123)
at
org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.initialise(ActionProcessingPipeline.java:259)
... 118 more
Could you send me your jboss-esb.xml for bpm_orchestration2 so I can try running it
instead ?
JMS Courrier does not support transacted mode
---------------------------------------------
Key: JBESB-1438
URL:
http://jira.jboss.com/jira/browse/JBESB-1438
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta, Documentation, Examples, Process flow
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
Assigned To: Daniel Bevenius
Priority: Blocker
Fix For: 4.2.1 CP1
Attachments: trans.tgz
JMS Courrier (deliver side) operates only with non-transacted queue sessions. This
prevents jBPM integration to work correctly. The problem can be sketched this way
1) The message is received via JMS/JCA listener, transaction is started
2) jBPM process is invoked
3) jBPM process sends message (calls service) in non-transacted mode
Three situations can happen
1) Exception is thrown later, it means that global transaction is rolled back but another
service was already invoked - BUG
2) jBPM process goes to the wait state and waits for response from ESB, global
transaction is committed, called service sends back signal to continue process - OK
3) jBPM process goes to the wait state and waits for response from ESB, called service
sends back signal to continue process - but the global transaction was not committed yet -
BUG
This is key feature to have ESB/jBPM integration working safely.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira