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

Bug 1168416

Summary: Implement async throwing signal events
Product: [Retired] JBoss BPMS Platform 6 Reporter: Alessandro Lazarotti <alazarot>
Component: jBPM CoreAssignee: Alessandro Lazarotti <alazarot>
Status: CLOSED EOL QA Contact: Radovan Synek <rsynek>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.3CC: kverlaen, mbaluch, tkobayas
Target Milestone: ER4   
Target Release: 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 20:11:32 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alessandro Lazarotti 2014-11-26 20:59:52 UTC
If we have several process instances from different process definitions, all of them waiting the same signal and only one of these process instances throws a RuntimeException all others not related will not move forward as well, because they are executed sequentially in the same single thread.

That creates a strong dependency between the process which are not in fact related.

Async signals can solve that, however they can potencially impact on performance given that each process will continue in a separated transaction. 
To solve this trade-off such behaviour should be configurable by users.

Comment 2 JBoss JIRA Server 2015-04-21 12:56:08 UTC
Maciej Swiderski <swiderski.maciej> updated the status of jira JBPM-4516 to Resolved

Comment 6 Radovan Synek 2015-10-19 14:00:41 UTC
Verified with BPMS-6.2.0.ER4