Bug 851503

Summary:	JBPM-3454 Repeating intermediate timer events will only fire if the attached process completes successfully.
Product:	[JBoss] JBoss Enterprise BRMS Platform 5	Reporter:	Maciej Swiderski <mswiders>
Component:	jBPM 5	Assignee:	Kris Verlaenen <kverlaen>
Status:	VERIFIED ---	QA Contact:	Marek Baluch <mbaluch>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	BRMS 5.3.0.GA	CC:	kverlaen
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	In cases where an unexpected error in the process flow occurred, the started by timer was not rescheduled properly, instead it was reregistered which caused duplicate executions. This was resolved by ensuring that timers are only registered once even when unexpected errors occur.	Story Points:	---
Clone Of:		Environment:
Last Closed:		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:

Description Maciej Swiderski 2012-08-24 11:29:27 UTC

Description of problem:
backport of https://issues.jboss.org/browse/JBPM-3454, in case of exception in any node after being started with timer timer will not be rescheduled properly

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


Actual results:
timer is not be rescheduled properly in case of exception in downstream nodes

Expected results:
timer should be rescheduled even exception is thrown to retry with next iteration

Additional info:

Comment 1 Maciej Swiderski 2012-08-24 12:06:16 UTC

backported into 5.2.x branch

Comment 2 Jiri Svitak 2012-09-20 09:36:31 UTC

Verified in BRMS 5.3.1 ER1.

Comment 3 Douglas Hoffman 2012-10-23 04:59:21 UTC

I have updated the Release Notes.

Thanks, Maciej.

- Doug

Comment 7 Jiri Svitak 2014-07-01 14:29:11 UTC

Fix commit:
https://github.com/droolsjbpm/jbpm/commit/9eb2748fedc56513e774a921bc8fd2a159765c2f