Bug 1281549 - KIE Server: jBPM extension ignore runtime strategy (and other settings) from deployment descriptor included in kjar
KIE Server: jBPM extension ignore runtime strategy (and other settings) from ...
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: Kie-Server (Show other bugs)
Unspecified Unspecified
urgent Severity high
: CR1
: 6.2.0
Assigned To: Maciej Swiderski
Ivo Bek
Depends On:
  Show dependency treegraph
Reported: 2015-11-12 13:21 EST by Maciej Swiderski
Modified: 2015-11-23 07:45 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Maciej Swiderski 2015-11-12 13:21:14 EST
Description of problem:
due to registration of async handler deployment descriptor included in kjar is ignored resulting with default settings taken as deployment descriptor while it should use these from kjar if exists

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

How reproducible:
as soon as kjar deployed to kie container has different settings than defaults - for example change runtime strategy to per process instance 

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
Comment 6 Ivo Bek 2015-11-23 07:44:04 EST
Verified in BPM Suite 6.2.0.CR1

Note: KIE Server performs significantly better in concurrent environment and with PerProcessInstance strategy used.

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