Bug 771840
| Summary: | Activations are not deleted after rollback | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Tomas Schlosser <tschloss> | ||||
| Component: | BRE (Expert, Fusion), jBPM 5 | Assignee: | lcarlon <lcarlon> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tomas Schlosser <tschloss> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | BRMS 5.3.0.GA | CC: | brms-jira, lpetrovi, mproctor | ||||
| Target Milestone: | --- | ||||||
| Target Release: | BRMS 5.3.0.GA | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-06-25 02:48:50 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: |
|
||||||
It seems the same mistake as in 771854 happened here. It is necessary to reload the session after rollback because the detached snapshot is not reverted automatically. If the session is reloaded, there are no activations present. Future course of action may be changing this behaviour so the session somehow reverts its state after the rollback. However in this moment it is necessary to at least document this behaviour to warn user that after every rollback, the session must be reloaded from the database. Assigning to Lee so that this doesn't fall off the grid. This is already documented in BRMS Business Process Management user guide. |
Created attachment 550843 [details] Simple reproducer Description of problem: When RuleFlow node is triggered in transaction and the transaction is then rolled back, the activation is not removed and after calling fireAllRules() the rule is fired. Version-Release number of selected component (if applicable): 5.3.0.ER1 How reproducible: Every time. Steps to Reproduce: 1. Run class RuleFlowGroup Actual results: Dummy rule fired no instance Expected results: no instance Additional info: Process creation is rolled back just fine.