Bug 807187 - Adhoc subprocess does not complete after triggering end event node inside
Summary: Adhoc subprocess does not complete after triggering end event node inside
Keywords:
Status: NEW
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM 5
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Kris Verlaenen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-27 08:58 UTC by Radovan Synek
Modified: 2023-05-31 22:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Ad-hoc sub-processes with non-terminating end event nodes do not end and the processes stays active.
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Radovan Synek 2012-03-27 08:58:20 UTC
Adhoc subprocess with tasks inside; each task is triggered by ksession.signal(). One of this tasks continues with non-terminating end event node, which is triggered but the adhoc subprocess does not complete and the process stays in active state.

there is a pull request with reproducer:
https://github.com/droolsjbpm/jbpm/pull/56

commit:
https://github.com/rsynek/jbpm/commit/c4dccc59d8951e88c74c1f4b6bfb34c1bdf57c31

Comment 1 lcarlon 2012-05-31 00:14:19 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Ad-hoc subprocesses with non-terminating end event nodes will not end and the process stays active.


Note You need to log in before you can comment on or make changes to this bug.