Bug 1002509
| Summary: | In Process Instances, finished instance shown also as active | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Zuzana Krejčová <zkrejcov> | ||||
| Component: | Business Central | Assignee: | Mauricio Salatino <msalatin> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Zuzana Krejčová <zkrejcov> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.0.0 | CC: | kverlaen, lpetrovi | ||||
| Target Milestone: | ER4 | ||||||
| Target Release: | 6.0.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-08-06 20:08:22 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: |
|
||||||
This is already fixed in master and 6.0.x since I couldn't reproduce the issue with the attached process. I've tested with H2 and it was working as expected. the Process is executed and the system.out appears in the console |
Created attachment 791702 [details] process-reproducer Description of problem: Shorter version - the business-central process instances perspective can show an instance both as active and as completed at the same time. Trying to abort such an instance fails with "Could not find process instance for id <id>" Longer version: You can create a process with a timer node that has an invalid duration defined. It is possible to run an instance of this process from the business-central. The timer node is immediately passed as if nothing is wrong. In the database, in processinstancelog table, there is both a record of this instance as active and as completed. This results in this instance shown in the business-central as both active and completed, since that is where the information about process instances is taken from for the gui. Unfortunately, if you try to abort this instance, you get an ugly stacktrace about "Could not find process instance for id <id>" - since that instance is not active any longer and is not therefore in the processinstanceinfo table. The process to reproduce this is attached. Tested on PostgreSQL 9.1. Version-Release number of selected component (if applicable): BPMS 6.0 ER2