Bug 806077
| Summary: | Process instance doesn't survive server restart | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Jiri Locker <jlocker> | ||||||
| Component: | jBPM Console | Assignee: | Kris Verlaenen <kverlaen> | ||||||
| Status: | CLOSED UPSTREAM | QA Contact: | |||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | BRMS 5.3.0.GA | ||||||||
| Target Milestone: | ER6 | ||||||||
| 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: | 2025-02-10 03:19: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: |
|
||||||||
Created attachment 572080 [details]
process does not finish
Problem is due to session is initialized on first access of Process Overview and that's why when completing task directly after server restart process is not triggered as there is no session available. So when user first access process overview instead to activate the session process instance will be resumed after completing the task. Nevertheless this is not desired to have to go to process tab to complete a task. Will make task management to be session initializer as well so regardless of accessing task or process management in console session will be already available. Pull request prepared, can be found at: https://github.com/droolsjbpm/jbpm/pull/65 This pull request has been merged into the 5.2.x and master branches. Update status to ON_QA. Please verify them against ER6. Verified in ER6. This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |
Created attachment 572079 [details] SimpleProcess.bpmn2 Description of problem: Running process instances are not picked up by the engine after server restart. I have a simple process with a single human task node between start and end nodes. After starting the process it is immediately persisted and waits for completion of the task node. At this point the server is restarted. When I complete the task now I expect the process will continue and end. After restarting the server, jBPM console correctly reports the running process instance and a pending task node but completing the task has no effect on the process instance. It will hang there forever. The ability of the jBPM engine to pick up process instances that were initiated by a different engine inside the same persistent knowledge session is necessary if we aim to support jBPM fail-over inside app server cluster. Version-Release number of selected component (if applicable): ER5 How reproducible: always Steps to Reproduce: 1. start the attached process 2. restart the server 3. complete the human task, process instance doesn't finish (see attached screenshot) Actual results: It isn't possible to continue the process instance after restarting the server. Expected results: After restarting the server, jBPM should restore all persisted process instances and continue executing them. In step 3 the process should finish after the task is completed. Additional info: