Red Hat Bugzilla – Bug 1311163
[GSS](6.2.z) Can't signal sub process when using the EJB API
Last modified: 2016-03-17 06:40:45 EDT
+++ This bug was initially created as a clone of Bug #1310820 +++
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):
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;
Error saying the process instance ID was not found.
Signal sent successfully.
A workaround is perform each action on a separated transaction or use no transaction at all in the client app.
--- Additional comment from JBoss Product and Program Management on 2016-02-22 12:40:08 EST ---
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
back ported to 6.3.x
Verified on BPM Suite 6.2.2 CR1