-
Bug
-
Resolution: Cannot Reproduce
-
Critical
-
None
-
jBPM 6.1.0.Final, jBPM 6.2.0.Beta1, jBPM 6.2.0.Beta2, jBPM 6.2.0.Beta3
-
Low
-
-
When using a singleton runtime manager strategy for managing process interfaction, in some processes with complex signals interactions, at some point broadcasting a signal (sending it without a process instance id) or message event stop working (anything happens), but sending the same signals or messages directed to the same process instances (sending them with the inclusion of the process instance id) works just fine.
If i try the same case but i rebuild (close and build another ) runtime manager before broadcasting the signal it works fine.
This bug dont include the boundry events, wich works just find in this case.
After debuging the RuntimeManager and related sources i found that the
problem seam to be that the message and signal EventNode's arenĀ“t marked with the scope "external" as are the signal and message BoundryEventNode's. This apparently cause that the list of broadcasting event listener is not properly populated.