Bug 1310820 - Can't signal sub process when using the EJB API
Can't signal sub process when using the EJB API
Status: VERIFIED
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: jBPM Core (Show other bugs)
6.1.0
Unspecified Unspecified
high Severity high
: ER1
: 6.3.0
Assigned To: Maciej Swiderski
Tomas Livora
:
Depends On:
Blocks: 1311163
  Show dependency treegraph
 
Reported: 2016-02-22 12:30 EST by William Antônio
Modified: 2016-03-17 06:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1311163 (view as bug list)
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description William Antônio 2016-02-22 12:30:09 EST
Description of problem:

If we have a process that has a human task followed by a sub process and when completing the task and trying to signal the started subprocess on the same transaction, we have an error saying that the subprocess does not exist. If we use no transaction, it works.

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

How reproducible:
always

Steps to Reproduce:
1. Create a simple process that has a human task following by a subprocess with a signal
2. use the jBPM EJB API to handle the process and user tasks;
3. on the same transaction (you can use a stateless EJB method with TransactionAttribute(REQUIRES_NEW) or any other that will preserve the tx), start a new process instance, start and complete the task, retrieve the subprocess ID and try to signal it;

Actual results:

Error saying the process instance ID was not found.


Expected results:

Signal sent successfully.

Additional info:

A workaround is perform each action on a separated transaction or use no transaction at all in the client app.
Comment 3 Tomas Livora 2016-03-17 06:07:06 EDT
Verified on BPM Suite 6.3.0 ER1

Note You need to log in before you can comment on or make changes to this bug.