Rohit Raghuwanshi [
http://community.jboss.org/people/rohit_r] created the discussion
"jBPM 3.2 Enterprise - Unhandled exception in async node?"
To view the discussion, visit:
http://community.jboss.org/message/564967#564967
--------------------------------------------------------------
Hello all,
We have a jBPM 3.2.7 Enterprise deployed on Websphere 7.0 / Oracle 10g
The process scenario is as follows
*START -> success-node (async) -> exception-node (async) -> END*
Each node just logs an message to console. When we start a new instance of the process
1. *success-node* logs the message.
2. *exception-node* throws an uncaught exception.
After this we find that if we check the process instance status, it shows up in
"*Running*" state with current node as *exception-node*. Is this the correct
behavior? We were expecting the process to get rolled back to end of *success-node*.
Also from this exception state if we signal the process further it goes to *END* state. We
were expecting the *exception-node* to get processed again as the transaction should have
rolled back to the end of *success-node*.
The process archive is attached. Would really appreciate some help here as the process
does not match our understanding of exception scenario in jBPM.
Thanks!
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/564967#564967]
Start a new discussion in jBPM at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]