Red Hat Bugzilla – Bug 1281549
KIE Server: jBPM extension ignore runtime strategy (and other settings) from deployment descriptor included in kjar
Last modified: 2015-11-23 07:45:07 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: 1. 2. 3. Actual results: Expected results: Additional info:
pull requests ready: master: https://github.com/droolsjbpm/droolsjbpm-integration/pull/231 6.3.x: https://github.com/droolsjbpm/droolsjbpm-integration/pull/232
pull requests merged into master and 6.3.x droolsjbpm-integration master: https://github.com/droolsjbpm/droolsjbpm-integration/commit/bee00cf897f0c047786a7d2620f6b08fb93d5a4f 6.3.x: https://github.com/droolsjbpm/droolsjbpm-integration/commit/c692ca7b1b1527135ae81b50e2e6360d9a2526f3
Verified in BPM Suite 6.2.0.CR1 Note: KIE Server performs significantly better in concurrent environment and with PerProcessInstance strategy used.