1:33 p.m.
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: Process flow, Rosetta
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
Assigned To: Mark Little
Priority: Blocker
Fix For: 4.2.1 CP1
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
10:43 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Mark Little reassigned JBESB-1438:
----------------------------------
Assignee: Daniel Bevenius (was: Mark Little)
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, Process flow
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
Assigned To: Daniel Bevenius
Priority: Blocker
Fix For: 4.2.1 CP1
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
5:59 p.m.
New subject: [JBoss JIRA] Work started: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Work on JBESB-1438 started by Daniel Bevenius.
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: Process flow, Rosetta
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
Assigned To: Daniel Bevenius
Priority: Blocker
Fix For: 4.2.1 CP1
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
6:45 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Daniel Bevenius updated JBESB-1438:
-----------------------------------
Component/s: Documentation
Examples
Will add quickstart: jms_transacted
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: Process flow, Rosetta, Documentation, Examples
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
Assigned To: Daniel Bevenius
Priority: Blocker
Fix For: 4.2.1 CP1
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
5:25 p.m.
New subject: [JBoss JIRA] Resolved: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Daniel Bevenius resolved JBESB-1438.
------------------------------------
Resolution: Done
Committed work in CP with revsion: 17869.
Effected files:
etc/schemas/xml/jbossesb-1.0.1.xsd
rosetta/src/org/jboss/internal/soa/esb/couriers/JmsCourier.java
rosetta/src/org/jboss/internal/soa/esb/rosetta/pooling/JmsConnectionPool.java
rosetta/src/org/jboss/internal/soa/esb/rosetta/pooling/JmsConnectionPoolContainer.java
rosetta/src/org/jboss/soa/esb/addressing/eprs/JMSEpr.java
rosetta/src/org/jboss/soa/esb/listeners/ListenerUtil.java
rosetta/src/org/jboss/soa/esb/listeners/config/mappers/JmsListenerMapper.java
rosetta/src/org/jboss/soa/esb/listeners/gateway/DefaultESBPropertiesSetter.java
rosetta/src/org/jboss/soa/esb/listeners/gateway/JmsGatewayListener.java
rosetta/src/org/jboss/soa/esb/notification/jms/DefaultJMSPropertiesSetter.java
rosetta/src/org/jboss/soa/esb/notification/jms/JMSPropertiesSetter.java
rosetta/tests/src/org/jboss/internal/soa/esb/couriers/JmsCourierIntegrationTest.java
rosetta/tests/src/org/jboss/internal/soa/esb/rosetta/pooling/JmsConnectionPoolContainerUnitTest.java
rosetta/tests/src/org/jboss/soa/esb/addressing/eprs/JMSEprUnitTest.java
rosetta/tests/src/org/jboss/soa/esb/listeners/config/jbossesb_config_01_esbaware.xml
rosetta/tests/src/org/jboss/soa/esb/listeners/config/jbossesb_config_01_gateways.xml
rosetta/tests/src/org/jboss/soa/esb/listeners/config/jbossesb_config_02.xml
rosetta/tests/src/org/jboss/soa/esb/listeners/gateway/DefaultESBPropertiesSetterUnitTest.java
samples/quickstarts/jms_transacted
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
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
7:26 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Mark Little closed JBESB-1438.
------------------------------
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
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
2:53 p.m.
New subject: [JBoss JIRA] Reopened: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Mark Little reopened JBESB-1438:
--------------------------------
Assignee: Mark Little (was: Daniel Bevenius)
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: Mark Little
Priority: Blocker
Fix For: 4.2.1 CP1
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
3:33 p.m.
New subject: [JBoss JIRA] Work started: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Work on JBESB-1438 started by Mark Little.
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: Mark Little
Priority: Blocker
Fix For: 4.2.1 CP1
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
4:22 p.m.
New subject: [JBoss JIRA] Work stopped: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Work on JBESB-1438 stopped by Mark Little.
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: Mark Little
Priority: Blocker
Fix For: 4.2.1 CP1
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
4:22 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=comments#action_12396843 ]
Mark Little commented on JBESB-1438:
------------------------------------
Does not deal with message outflow.
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
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
4:22 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Mark Little reassigned JBESB-1438:
----------------------------------
Assignee: Daniel Bevenius (was: Mark Little)
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
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
5:04 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-1438) JMS Courrier does not support transacted mode
[ 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
8:18 p.m.
New subject: [JBoss JIRA] Work started: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Work on JBESB-1438 started by Daniel Bevenius.
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
1 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=comments#action_12396993 ]
Daniel Bevenius commented on JBESB-1438:
----------------------------------------
I've made a few changes to the code to make sure that the JMSCourier infact does use
transacted session for picking up messages and for sending messages.
But I don't understand how the quickstart is supposed to prove that transaction are
working properly with jBPM.
This is my understanding of the quickstart:
1. 'ant startProcess' create a file that is picked up by the file gateway.
2. The file contents is packaged and sent via a JMSCourier that is transacted.
3. Action pipeline is invoked and "MessageSpy: Body: Start it up" is printed.
4. jBPM process "processDefinition2" is started by in action pipleline.
1. start-state has a transition to "node1". The transistion contains an
action named "action1".
action1 calls the ESB Service "Service0" which uses a JMSCourier that is
transacted.
Service0 executes /scripts/service0.groovy and prints:
"********** This should be second ***********"
2. node1 is entered and its "node-enter" event is executed.
The "node-enter" event will sleep(5000) and then prints "***** This
should be first *****"
Next the action of node1 will be executed and call Service1 using a JMSCourier
that is transacted.
Service1 executes executes /scripts/service1.groovy
...
Sorry if I missing something obvious here but I can't see how this proves that
transactions are working of not.
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
1:14 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=comments#action_12396995 ]
Jiri Pechanec commented on JBESB-1438:
--------------------------------------
The problem is that the transaction is committed when it comes to the node Service1 that
calls service1.groovy. So it means that if the JMSCourrier sends messages that
participates in global transaction. then the message is delivered to queue if and only if
the commit is done in node Service1 after execution of action EsbActionHandler.
You can also change the script that contains Thread.sleep to throw NullPointerException().
In that case the global transaction is rolled-back and the message should never be sent.
I think the gross misunderstanding is due to partly invalid issue description. What I
excatly need is that the JMS message sending is enlistened to running XA transaction,
whcih is of course different from JMS session transaction mode. Sorry for the confusion.
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
1:32 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=comments#action_12396996 ]
Daniel Bevenius commented on JBESB-1438:
----------------------------------------
Ah now I get it, thanks Jiri for clearing that up.
Perhaps I should create a new Jira for this to avoid confusion.
The work for this Jira should be enough for enlisting all resources in one service (action
pipeline) in the same transaction.
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
5:47 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=comments#action_12397059 ]
Kevin Conner commented on JBESB-1438:
-------------------------------------
Daniel, I have fully asynchronous jBPM callbacks working and it shows up this problem
using bpm_orchestration2.
I can help to verify any fix.
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
7:03 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1438) JMS Courrier does not support transacted mode
[ 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
3 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=comments#action_12397173 ]
Kevin Conner commented on JBESB-1438:
-------------------------------------
Does you version still deploy the process through the jboss-esb? If so, Kurt has recently
removed support for this but the QS should have been updated.
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
3:12 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=comments#action_12397176 ]
Daniel Bevenius commented on JBESB-1438:
----------------------------------------
yep, there is a service that deploys the process. Is it not needed anymore? How do
processes get deploy nowadays?
The quickstart is not checked into svn, but attached to this Jira.
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
4 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=comments#action_12397191 ]
Kevin Conner commented on JBESB-1438:
-------------------------------------
The service should be removed from the jboss-esb.xml file as this is handled through an
ant task which Kurt wrote. The process deployment now uses a standard jBPM mechanism,
uploading a process archive through the jBPM upload servlet.
The best idea would be to look at the bpm_orchestration1 QS and pull in the changes to the
build.xml and jboss-esb.xml, I can help out if needed.
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
4:47 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=comments#action_12397200 ]
Daniel Bevenius commented on JBESB-1438:
----------------------------------------
I've tried removing the service that deploys the process and it now deploys correctly.
When I run 'ant startProcess' I no longer get the expected output.
I noticed that this warning is displayed :
[ProxyWarnLog] Narrowing proxy to class org.jbpm.graph.node.StartState - this operation
breaks ==
This is also displayed when I run bpm_orchestration1. Anyone seen this before and could it
cause the output to no longer be printed?
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
8:28 a.m.
New subject: [JBoss JIRA] Work stopped: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Work on JBESB-1438 stopped by Daniel Bevenius.
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
11:50 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Mark Little reassigned JBESB-1438:
----------------------------------
Assignee: Mark Little (was: Daniel Bevenius)
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: Mark Little
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
11:50 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=comments#action_12397298 ]
Mark Little commented on JBESB-1438:
------------------------------------
Taking this from Daniel as discussed with him.
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: Mark Little
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
2 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Mark Little reassigned JBESB-1438:
----------------------------------
Assignee: Kevin Conner (was: Mark Little)
Assigning this to Kevin for now as I haven't had a chance to finish it. Assign it back
later if necessary.
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: Kevin Conner
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
1:51 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Mark Little reassigned JBESB-1438:
----------------------------------
Assignee: Mark Little (was: Kevin Conner)
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: Mark Little
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
1:51 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Mark Little closed JBESB-1438.
------------------------------
Resolution: Done
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: Mark Little
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
5:17 p.m.
New subject: [JBoss JIRA] Reopened: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Kevin Conner reopened JBESB-1438:
---------------------------------
Unfortunately there are still circumstances in which the JMS message is not enlisted into
the transaction.
Will discuss further with Mark this evening.
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: Process flow, Rosetta, Documentation, Examples
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
Assigned To: Mark Little
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
2:39 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-1438) JMS Courrier does not support transacted mode
[ http://jira.jboss.com/jira/browse/JBESB-1438?page=all ]
Mark Little closed JBESB-1438.
------------------------------
Resolution: Done
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: Mark Little
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
4:19 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1438) JMS Courrier does not support transacted mode
[
https://jira.jboss.org/jira/browse/JBESB-1438?page=com.atlassian.jira.plu...
]
Bernd Ruecker commented on JBESB-1438:
--------------------------------------
I think this bug is still or again in the product, see
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193474
Maybe this bug should be reopened?
JMS Courrier does not support transacted mode
---------------------------------------------
Key: JBESB-1438
URL: https://jira.jboss.org/jira/browse/JBESB-1438
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Documentation, Examples, Process flow, Rosetta
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
Assignee: Mark Little
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:33 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1438) JMS Courrier does not support transacted mode
[
https://jira.jboss.org/jira/browse/JBESB-1438?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-1438:
-------------------------------------
To the best of our knowledge this bug no longer exists in the product. I suspect you are
seeing something different but we should pursue this on the forums until we can identify
what it is.
JMS Courrier does not support transacted mode
---------------------------------------------
Key: JBESB-1438
URL: https://jira.jboss.org/jira/browse/JBESB-1438
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Documentation, Examples, Process flow, Rosetta
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
Assignee: Mark Little
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5686
days inactive
6018
days old
31 comments
5 participants
participants (5)
-
Bernd Ruecker (JIRA) -
Daniel Bevenius (JIRA)
-
Jiri Pechanec (JIRA)
-
Kevin Conner (JIRA)
-
Mark Little (JIRA)