I created two persistent knowledge sessions and in each session I started one process instance, then I disposed of the two sessions. Both process instances are instances of same process definition which has only one wait node of type signal event.
Later on, I load the second session from JPA datastore based on its id and I fire the event for which the two process instances are waiting. I fire this event on the knowledge session [ie ksession.signalEvent("LastCheckEvent", null);], not on the process instance itself.
After I do that, both process instances advanced to the end node, even though I only loaded the second session from JPA datastore. This makes me think event instances fired within the context of a given session, don't know to which instance to dispatch the event. It would be nice to only dispatch the signaled event to the process that was started within loaded session.