Bug 1121764
Summary: | Spring/JBPM: IllegalStateException: RuntimeManager with id spring-rmr is already active | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Josh West <jowest> | ||||
Component: | jBPM Core | Assignee: | Alessandro Lazarotti <alazarot> | ||||
Status: | CLOSED EOL | QA Contact: | Ivo Bek <ibek> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 6.0.2 | CC: | ksuta | ||||
Target Milestone: | DR2 | ||||||
Target Release: | 6.1.0 | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2020-03-27 20:11:42 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: | |||||||
Attachments: |
|
Description
Josh West
2014-07-21 19:51:04 UTC
fix applied for both master and 6.1.x branch droolsjbpm-integration master: https://github.com/droolsjbpm/droolsjbpm-integration/commit/da1bec7ee52ef51877fca0879856905df15be3ce droolsjbpm-integration 6.1.x: https://github.com/droolsjbpm/droolsjbpm-integration/commit/bf29365c81ab8cce79f175f4d2ccb2e528e128ca Verified in BPMS 6.1.0.DR2 To verify this issue, I used the reproducer. However, it requires some changes to make it working with the current release. First, I removed FixedRuntimeManagerFactoryBean and replaced it with org.kie.spring.factorybeans.RuntimeManagerFactoryBean to reproduce the problem. I should also mention that I used PostgreSQL instead of OracleDB. I successfully reproduced the problem and then I have done the changes that happened meanwhile, see the attached diff.txt file. I just worry that some code will change in future and it will be necessary to update it again because for example JPATaskLifeCycleEventListener has changed and now it requires some boolean flag (called "flag") in the constructor that is not used and I have no idea what will be its purpose. Created attachment 935375 [details]
diff.txt
(In reply to Ivo Bek from comment #3) > Verified in BPMS 6.1.0.DR2 > > To verify this issue, I used the reproducer. However, it requires some > changes to make it working with the current release. > > First, I removed FixedRuntimeManagerFactoryBean and replaced it with > org.kie.spring.factorybeans.RuntimeManagerFactoryBean to reproduce the > problem. I should also mention that I used PostgreSQL instead of OracleDB. I > successfully reproduced the problem and then I have done the changes that > happened meanwhile, see the attached diff.txt file. > > I just worry that some code will change in future and it will be necessary > to update it again because for example JPATaskLifeCycleEventListener has > changed and now it requires some boolean flag (called "flag") in the > constructor that is not used and I have no idea what will be its purpose. Ivo, this constructor was added to make it non CDI bean - no default constructor otherwise it would cause issues - meaning always be available for injections. As you noticed it does not do anything it's there just to prevent cdi of finding it. |