Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1068744

Summary: Boundary error catching event breaks process simulation
Product: [Retired] JBoss BPMS Platform 6 Reporter: Babak Mozaffari <bmozaffa>
Component: jBPM DesignerAssignee: Maciej Swiderski <mswiders>
Status: CLOSED CURRENTRELEASE QA Contact: Sona Mala <smala>
Severity: medium Docs Contact:
Priority: high    
Version: 6.0.0CC: kverlaen, rrajasek, tsurdilo
Target Milestone: ER2   
Target Release: 6.0.1   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:02:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Sample process to reproduce error none

Description Babak Mozaffari 2014-02-21 19:38:52 UTC
Created attachment 866226 [details]
Sample process to reproduce error

Description of problem:

Placing a boundary event to catch errors and loop back, first to a user task and then to the node, would be a common pattern to correct and retry external calls. However process simulation appears to see this as an infinite loop and results in stack overflow.


Version-Release number of selected component (if applicable):

6.0.0 GA

How reproducible:

Consistent


Steps to Reproduce:
1. Create a process as described or used attached process
2. In web designer, use process simulation to show paths
3. Check log for stack overflow error

Actual results:

Stack overflow error

Expected results:

Successful process simulation

Additional info:

Comment 3 Sona Mala 2014-03-10 09:25:20 UTC
I verify that simulation returns results in 6.0.1 ER2 for process which uses Boundary Event.

Unfortunately, the results are incorrect. I will create new bugzilla's issues.

The main issue is that boundary event is simulated incorrect (for both Simulations - Path, Run).