[jbpm-issues] [JBoss JIRA] Updated: (JBPM-2950) HibernateException is thrown during concurrent Timers persistence
[
https://jira.jboss.org/browse/JBPM-2950?page=com.atlassian.jira.plugin.sy...
]
Borislav Andruschuk updated JBPM-2950:
--------------------------------------
Description:
We deploy ProcessDefinition on application startup and use this one persisted instance
during application activity in several threads (i.e. during full application live time).
We noticed that during concurrent Timers creation for several processes which build from
this ProcessDefinition instance we've got:
{quote}
org.hibernate.HibernateException: identifier of an instance of org.jbpm.graph.def.Action
was altered from 532 to 533
{quote}
After investigation I've noticed that Action instance is persisted anew (not updated)
in concurrent threads and new row appears in the table. The problematic place is in
org.jbpm.db.JobSession.saveJob where Action is checked on existence in Hibernate
Session's persistent context. The suggested fix is to changed condition:
{quote}
!session.contains(action)
{quote}
to
{quote}
action.getId() == 0L
{quote}
This change fixes our problem.
was:
We deploy ProcessDefinition on application startup and use this one persisted instance
during application activity in several threads (i.e. during full application live time).
We noticed that during concurrent Timers creation for several processes which build from
this ProcessDefinition instance we've got:
org.hibernate.HibernateException: identifier of an instance of org.jbpm.graph.def.Action
was altered from 532 to 533
After investigation I've noticed that Action instance is persisted anew (not updated)
in concurrent threads and new row appears in the table. The problematic place is in
org.jbpm.db.JobSession.saveJob where Action is checked on existence in Hibernate
Session's persistent context. The suggested fix is to changed condition:
!session.contains(action)
to
action.getId() == 0L
This change fixes our problem.
HibernateException is thrown during concurrent Timers persistence
-----------------------------------------------------------------
Key: JBPM-2950
URL: https://jira.jboss.org/browse/JBPM-2950
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Borislav Andruschuk
We deploy ProcessDefinition on application startup and use this one persisted instance
during application activity in several threads (i.e. during full application live time).
We noticed that during concurrent Timers creation for several processes which build from
this ProcessDefinition instance we've got:
{quote}
org.hibernate.HibernateException: identifier of an instance of org.jbpm.graph.def.Action
was altered from 532 to 533
{quote}
After investigation I've noticed that Action instance is persisted anew (not updated)
in concurrent threads and new row appears in the table. The problematic place is in
org.jbpm.db.JobSession.saveJob where Action is checked on existence in Hibernate
Session's persistent context. The suggested fix is to changed condition:
{quote}
!session.contains(action)
{quote}
to
{quote}
action.getId() == 0L
{quote}
This change fixes our problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira