Bug 1168416 – Implement async throwing signal events

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1168416 - Implement async throwing signal events

Summary:	Implement async throwing signal events

Status:	VERIFIED

Aliases:	None

Product:	JBoss BPMS Platform 6
Classification:	Retired
Component:	jBPM Core (Show other bugs)
Sub Component:
Version:	6.0.3
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	ER4
Target Release:	6.2.0
Assigned To:	Maciej Swiderski
QA Contact:	Radovan Synek
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2014-11-26 15:59 EST by Alessandro Lazarotti
Modified:	2015-10-19 10:00 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	Feature Request
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	JBPM-4516	Major	Resolved	Implement async throwing signal events	2018-04-24 04:30 EDT
JBoss Issue Tracker	PRODMGT-1172	Major	Pending Product Management Triage	Implement async throwing signal events	2018-04-24 04:30 EDT

Groups: None (edit)

Description Alessandro Lazarotti 2014-11-26 15:59:52 EST

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 08:56:08 EDT

Maciej Swiderski <swiderski.maciej@gmail.com> updated the status of jira JBPM-4516 to Resolved

Comment 3 Maciej Swiderski 2015-04-22 13:54:21 EDT

see comment in jira [1] for details about implementation and commit [2] for test cases

[1] https://issues.jboss.org/browse/JBPM-4516?focusedCommentId=13061037&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13061037

[2]https://github.com/droolsjbpm/jbpm/commit/5d3c47130d037bddce4f31841a8e123b66021e9f

Comment 6 Radovan Synek 2015-10-19 10:00:41 EDT

Verified with BPMS-6.2.0.ER4

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