Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1194180

Summary: SessionNotFoundException when using Reusable sub-process with [Wait For Completion] = false and Per_Process_Instance strategy
Product: [Retired] JBoss BPMS Platform 6 Reporter: Lyle Wang <lywang>
Component: jBPM CoreAssignee: Alessandro Lazarotti <alazarot>
Status: CLOSED EOL QA Contact: Marek Baluch <mbaluch>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.2CC: hritchie, kverlaen, mbaluch
Target Milestone: ER6   
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 20:03:55 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:
Description Flags
01360830-Reusable_Sub-process.zip
none
error.log none

Description Lyle Wang 2015-02-19 09:35:56 UTC
Created attachment 993521 [details]
01360830-Reusable_Sub-process.zip

Description of problem:


When calling a sub-process using Reusable sub-process, and [Wait For Completion] = false.
The main (parent) process gets Completed once the sub-process is called, and sub-process contains a timer which will take some time before completion.

On the sub-process's completion, get "SessionNotFoundException" exception. 
Attaching the stacktrace as "error.log";
The process definitions are attached as "01360830-Reusable_Sub-process.zip"

This only happens when 1) using "Per-Process-Instance" runtime strategy  AND  2) set [Wait For Completion] = false for Reusable sub-process.

The tasks inside the sub-process seem all executed with no issue, the error happens when the sub-process finishes.


Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:

1) install clean bpms 6.0.2 and create a project in business-central
2) in business-central, import the 2 process def.  and build/deploy
3) in business-central, go to "Deploy - Deployments", remove the default "Singleton" deployment unit, create a new one with "Per_Process_Instance" strategy
4) start a parentprocess  instance, type something whatever you like as input data



Actual results:

all process instances finish with no error


Expected results:

error happens as in error.log

Additional info:

Comment 1 Lyle Wang 2015-02-19 09:37:44 UTC
Created attachment 993522 [details]
error.log

Comment 3 Lyle Wang 2015-02-19 09:54:53 UTC
Sorry, incorrect "Actual results" and "Expected results" order in bug description section.


Should be:

-------------------------
Actual results:

error happens as in error.log


Expected results:

all process instances finish with no error

-------------------------

Comment 4 Maciej Swiderski 2015-02-19 17:13:07 UTC
fixed on master

jbpm
master:
https://github.com/droolsjbpm/jbpm/commit/59e55a6ee629ef8c01be43d7b2565d2ca7a2412e

in case it shall be back ported to 6.2.x please assign back to me.

Comment 5 Kris Verlaenen 2015-02-20 12:47:36 UTC
Since this is a simple fix related to a customer request, I believe we should backport to 6.2.x as well.

Comment 6 Maciej Swiderski 2015-02-20 13:04:01 UTC
backported to 6.2.x

jbpm
6.2.x:
https://github.com/droolsjbpm/jbpm/commit/e90d56866f4b7e6b67923db74803b2a11c138f7e

Comment 7 Jiri Svitak 2015-03-17 10:51:23 UTC
Verified in BPM Suite 6.1.0.ER6.

QE test coverage:
https://gitlab.mw.lab.eng.bos.redhat.com/bxms/brms/commit/17a68f73c4f510fbed8e2116c4147abf0cf40b86

Comment 9 cshumake 2015-09-14 19:18:19 UTC
The steps for reproduction seem to differ from the support ticket. While the scenario in this BZ makes more sense, is it possible that the support ticket case is problematic too?

Specifically, the support ticket says when "Wait For Completion" is true, not false.

https://access.redhat.com/solutions/1355423

Comment 10 Lyle Wang 2015-09-15 03:43:23 UTC
To confirm, the condition to reproduce the issue is "Wait For Completion"=false