Bug 993453 - Using external component to handle jBPM5 timer
Using external component to handle jBPM5 timer
Status: NEW
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM 5 (Show other bugs)
BRMS 5.3.1
All All
unspecified Severity medium
: ---
: ---
Assigned To: Kris Verlaenen
Radovan Synek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-05 21:04 EDT by David Tse
Modified: 2015-07-08 13:31 EDT (History)
1 user (show)

See Also:
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: ---


Attachments (Terms of Use)
Source codes and jars for using quartz timer (1.76 MB, application/x-zip-compressed)
2013-08-05 22:43 EDT, David Tse
no flags Details

  None (edit)
Description David Tse 2013-08-05 21:04:12 EDT
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-05 22:43:30 EDT
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.

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