This content has been marked as final.
Show 3 replies
-
1. Re: Is that possible to create a non-persisted ProcessInstan
boercher Apr 8, 2009 5:25 AM (in response to kenees)Have you tried to remove the offending object(s) from the Hibernate session? I don't know if it is possible to access it in the right moment but I would try
jbpmContext.getSession().evict(processInstance)
(or the like)
BTW: Doesn't it help to omit the call to jbpmContext.save() ?
Volker -
2. Re: Is that possible to create a non-persisted ProcessInstan
kenees Apr 8, 2009 5:36 AM (in response to kenees)"boercher" wrote:
Have you tried to remove the offending object(s) from the Hibernate session? I don't know if it is possible to access it in the right moment but I would tryjbpmContext.getSession().evict(processInstance)
(or the like)
BTW: Doesn't it help to omit the call to jbpmContext.save() ?
Volker
Hi Volker, I will try it, but it sounds like a hack? It seems I can and JBPM provides the ability to specify what process instances should be saved and what shouldn't. -
3. Re: Is that possible to create a non-persisted ProcessInstan
kenees Apr 8, 2009 5:44 AM (in response to kenees)Hi Volker
Unfortunately, your hack doesn't work, I got a more serious exception:17:41:04,598 ERROR [AssertionFailure] an assertion failure occured (this may indicate a bug in Hiber nate, but is more likely due to unsafe use of the session) org.hibernate.AssertionFailure: possible nonthreadsafe access to session at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:64) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:167) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingE ventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java: 27)