Bug 993453

Summary: Using external component to handle jBPM5 timer
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: David Tse <dtse>
Component: jBPM 5Assignee: Kris Verlaenen <kverlaen>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: BRMS 5.3.1   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
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:
Attachments:
Description Flags
Source codes and jars for using quartz timer none

Description David Tse 2013-08-06 01:04:12 UTC
Description of problem:
jBPM5 persists BPMN2 timer info in the session info in order for the timers to activate.  When an application requires extensive use of timer, a large number of sessions must be kept active in memory.  An alternative solution for this kind of requirement is to delegate those timers to an external component such as Quartz scheduler.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 David Tse 2013-08-06 02:43:30 UTC
Created attachment 783141 [details]
Source codes and jars for using quartz timer

Will provide an updated version for eap6-mdb to make the quartz code more generic.