Bug 1267661
Summary: | Signalling the process instance results in error message | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Pavel Kralik <pkralik> | ||||
Component: | Business Central | Assignee: | Marco Rietveld <mrietvel> | ||||
Status: | CLOSED EOL | QA Contact: | Lukáš Petrovický <lpetrovi> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 6.2.0 | CC: | kverlaen | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2020-03-27 20:01:39 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 error indicates that process instance has already been completed. Most likely due to timer expired and completed process instance. I just double checked that this does work fine for active process instance deployed with per process instance strategy. Pavel, do you mind double checking if the reason for this failure is as described above? Hi Maciej, Process instances and tasks list in Active tab shows tasks and Proc. Instances that are completed too. https://bugzilla.redhat.com/show_bug.cgi?id=1270690 Would it be possible to have modal dialog with user friendly message stated something like "trying to signal completed process instances"? Employee 'msalatin' has left the company. |
Created attachment 1078703 [details] Error signal dialog Description of problem: When trying to signal process instance through Options > Signal in the Details panel the error modal dialog appears Version-Release number of selected component (if applicable): BPMS 6.2.0.ER3 How reproducible: Always Steps to Reproduce: 1. Go to the process instances and select the details tab for the instance eg. simple timer 2. Set the Options > Signal 3. Error modal dialog appears: Exception thrown: No session found for context 6 4. Hit "Ok" and "Signaling process instance" (should be "Signalling") appears 5. Hit "Signal" button with empty values and error dialog is thrown again Actual results: Error message with user unfriendly message Expected results: Signal dialog appears Additional info: ERROR [org.guvnor.common.services.backend.exceptions.ExceptionUtilities] (http-/127.0.0.1:8080-21) Exception thrown: No session found for context 6: org.kie.internal.runtime.manager.SessionNotFoundException: No session found for context 6 at org.jbpm.runtime.manager.impl.PerProcessInstanceRuntimeManager$PerProcessInstanceInitializer.initKieSession(PerProcessInstanceRuntimeManager.java:486) [jbpm-runtime-manager-6.3.0.Final-redhat-1.jar:6.3.0.Final-redhat-1] at org.jbpm.runtime.manager.impl.RuntimeEngineImpl.getKieSession(RuntimeEngineImpl.java:70) [jbpm-runtime-manager-6.3.0.Final-redhat-1.jar:6.3.0.Final-redhat-1]