In my project, I have created a StatefulKnowledgeSession that is
persistent. The StateulfKnowledgeSession implementation is the
CommandBasedStatefulKnowledgeSession. From this
CommandBasedStatefulKnowledgeSession, I started a workflow that contains a
SignalEvent waiting for something to signal into that process.
I then started a second process that contains only an action node with the
SignalHello"); // Should broadcast to all other processes currently
running in this session.
The signal is never received by the first process because the
kcontext.getKnowledgeRuntime() that is trying to signal the event uses an
instance of StatefulKnowledgeSessionImpl not
CommandBasedStatefulKnowledgeSession. Can anyone explain why the
kcontext.getKnowledgeRuntime() returns a different instance of the
StatefulKnowledgeSession than the one it was started with? Is this a bug?
Show replies by date