Bug 1015323

Summary: Timer nullpointer due to race condition during update
Product: [Retired] JBoss BRMS Platform 6 Reporter: Mark Proctor <mproctor>
Component: BREAssignee: Mario Fusco <mfusco>
Status: CLOSED CURRENTRELEASE QA Contact: Marek Winkler <mwinkler>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: etirelli, lpetrovi, mfusco
Target Milestone: ER5   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:20:35 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:

Description Mark Proctor 2013-10-03 23:01:03 UTC 
If the timer fires at the same time as an update it results in the child being propagated twice. We need to synchronize to ensure that this does not happen. The update should cancel the timer, so it doesn't try and schedule a propagation.
Comment 1 JBoss JIRA Server 2013-10-03 23:03:13 UTC 
Mark Proctor <mproctor> updated the status of jira DROOLS-284 to Resolved
Comment 3 Mario Fusco 2013-10-04 08:08:29 UTC 
Fixed by Mark with this commit: https://github.com/droolsjbpm/drools/commit/859b1a5915fe89ba37483afc84c6dd00fe07878a
Comment 4 Marek Winkler 2013-12-12 16:59:05 UTC 
Verified on BRMS 6.0.0 ER5.