Boundary Event associated to a User Task is listening for the signal even when the User Task is not active

Solution Verified - Updated -

Issue

  • It has been observed that Boundary Event associated to a User Task is listening for the signal even when the User Task is not active. To prove this behavior , attached is a sample jBPM6 Project which can be imported in JBDS or any Eclipse based IDE and execute the ProcessMain.java class to reproduce the problem. Is this expected behaviour?
  • In short the process which has the following sequence of flows can cause the problem upon receiving the signal.
Start -> Signal -> XOR gateway (Converging) -> Script Task -> User task 
(having a Boundary Event) -> End

 User task (having a Boundary Event) -> XOR gateway (Converging) -> Script Task -> User task (having a Boundary Event) -> End

As it can be seen from above flows there are two signal events and they both use the same SignalRef SignalOne , and when the process is instantiated it waits for signal to continue moving forward. Now, the problem is that when the process instance is signalled , it is observed that the script task is executed twice.

Environment

  • Red Hat JBoss BPM Suite (BPMS)
    • 6.0.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.