-
1. Re: Weird problem with new JBPM 5.2 release
swiderski.maciej Dec 13, 2011 2:57 PM (in response to mpiraccini)Do you create new session or load it from the data base?
I had similar issue (can't say it was exactly the same) that was caused by incompatible session snapshots in db, unfortunately could not find out what was the root of the incompatibility but after creating session instead of loading resolved the problem.
HTH
-
2. Re: Weird problem with new JBPM 5.2 release
mpiraccini Dec 14, 2011 3:08 AM (in response to mpiraccini)I answer to my own question. In my code, to avoid to dipose the session "manually", I manage the afterProcessCompleted event:
public void afterProcessCompleted(ProcessCompletedEvent event)
{
// Dispose the session.
// Commented with JBPM 5.2
((StatefulKnowledgeSession) event.getKnowledgeRuntime()).dispose();
}
That turns to null the session.
With JBPM 5.2, after the process is completed, the InternalKnowledgeRuntime.endOperation is executed, soi a NPE is thrown.