[
http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Jiri Pechanec updated JBESB-1438:
---------------------------------
Attachment: trans.tgz
I am attaching the example that should prove if transaction sending works or not. The test
is based on bpm_orchestration1 quickstart.
There is a EsbNotifier action attached to transition from start node to the first one. The
aciton prints message: ********** This should be second ***********
On the first node there is a node-enter event that sleeps for 5 seconds and then prints
message: ***** This should be first *****
The expected output of the test is 5 seconds no action, then messages
***** This should be first *****
********** This should be second ***********
If transactions are not working then the messages comes in opposite order.
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