Bug 833609
Summary: | JPAKnowledgeService sessions fail on CMT under other App Servers | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Babak Mozaffari <bmozaffa> |
Component: | BRE (Expert, Fusion) | Assignee: | Nobody <nobody> |
Status: | VERIFIED --- | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | BRMS 5.3.0.GA | CC: | kverlaen |
Target Milestone: | ER2 | ||
Target Release: | BRMS 5.3.1 GA | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Running JBoss Enterprise BRMS Business Process Management in a CMT environment caused a NullPointerExpection on WebSphere, because it did not allow access to UserTransaction, this made it impossible to run processes in the CMT environment. This has been resolved by implementing a dedicated TransactionManager to allow processes to run in the CMT environment.
|
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: |
Description
Babak Mozaffari
2012-06-19 21:10:19 UTC
Added dedicated TransactionManager (drools TM) implementation that fits CMT mode by assuming transaction is active and begin/rollback/commit is no-op. TransactionSynchronization is used as usual as WAS allows access to TransactionSynchronizationRegistry via JNDI lookup. More information about it together with details on required configuration can be found in documentation section attached to this implementation (commit https://github.com/droolsjbpm/jbpm/commit/0ccc9a4f9e02f1fb2464344b5c395998f6cfda2d) Most important is that since rollback is no-op, user implementation (inside business method of EJB, for example) must propagate all exceptions thrown by the engine up to container to properly rollback transaction managed by container. Verified on 5.3.1.BRMS-ER3 |