Bug 1076361

Summary:	Event expiration calculation may overflow
Product:	[Retired] JBoss BRMS Platform 6	Reporter:	Mario Fusco <mfusco>
Component:	BRE	Assignee:	Mario Fusco <mfusco>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Tomas Schlosser <tschloss>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.0.0	CC:	kverlaen, mbaluch
Target Milestone:	ER1
Target Release:	6.0.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-06 19:54:36 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 Mario Fusco 2014-03-14 08:12:07 UTC

The calculation of the expiration timestamp of an event in the OTN is effectively given by the combination :

Handle.startTimeStamp + Handle.duration + OTN.expirationOffset 

If the addition overflows, the event will be scheduled for expiration immediately.

Comment 1 Mario Fusco 2014-03-14 08:12:58 UTC

Fixed by https://github.com/droolsjbpm/drools/commit/efcdfa0e4

Comment 2 JBoss JIRA Server 2014-03-14 08:14:15 UTC

Mario Fusco <mario.fusco> updated the status of jira DROOLS-455 to Resolved

Comment 4 Tomas Schlosser 2014-05-06 09:20:50 UTC

Verified with BRMS 6.0.2 ER2.