org.hibernate.StaleObjectStateException: jbpm and esb

[sshetty]

Hi,

We see the following invocation when we use JBPM to orchestrate our ESB services.

2009-03-02 16:00:07,508 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
2009-03-02 16:00:07,508 DEBUG [org.hibernate.jdbc.ConnectionManager] skipping aggressive-release due to flush cycle
2009-03-02 16:00:07,508 ERROR [org.hibernate.event.def.AbstractFlushingEventListener] Could not synchronize database state with session
org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.job.ExecuteActionJob#63081]
 at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1765)
 at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2407)
 at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2307)
 at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2607)
 at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:92)
 at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:250)
 at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:234)
 at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:142)
 at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
 at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
 at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
 at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338)
 at org.hibernate.transaction.CacheSynchronization.beforeCompletion(CacheSynchronization.java:59)
 at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:114)
 at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:247)
 at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:86)
 at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177)
 at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1389)
 at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
 at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87)
 at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:140)
 at org.jbpm.persistence.jta.JtaDbPersistenceService.endJtaTransaction(JtaDbPersistenceService.java:76)
 at org.jbpm.persistence.jta.JtaDbPersistenceService.close(JtaDbPersistenceService.java:37)
 at org.jbpm.svc.Services.close(Services.java:225)
 at org.jbpm.JbpmContext.close(JbpmContext.java:139)
 at org.jbpm.job.executor.JobExecutorThread.acquireJobs(JobExecutorThread.java:144)
 at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:58)
2009-03-02 16:00:07,509 DEBUG [org.hibernate.jdbc.ConnectionManager] aggressively releasing JDBC connection
2009-03-02 16:00:07,509 DEBUG [org.hibernate.jdbc.ConnectionManager] releasing JDBC connection [ (open PreparedStatements: 0, globally: 0) (open ResultSets: 0, globally: 0)]
2009-03-02 16:00:07,510 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_2] TwoPhaseCoordinator.beforeCompletion - failed fo
r com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@53a642

Here is our env:

Oracle 10g
jboss-4.2.3.GA
jboss-messaging-1.4.2.GA
jbossesb-4.4.GA

Our BPM does not use fork or joins.

Any help appreciated.

Thanks

:)
SShetty

[sshetty]

Forgot to mention, we have clustered 2 servers on 2 different hosts. And the BPM can trigger on either host.

Thanks

:)
SShetty

[bradsdavis]

What type of caching are you using with jboss?

[bradsdavis]

I mean, what type of caching are you using with Hibernate?

[sshetty]

Hi Brad,

We are using the EhCacheProvider instead of the default org.hibernate.cache.HashtableCacheProvider.

<property name="hibernate.cache.provider_class">net.sf.ehcache.hibernate.EhCacheProvider</property>

Thanks

:)
SShetty

[jbarrez]

I assume you have multiple JobExecutors going.

Then the StaleObject exceptions are to be expected when multiple threads try to lock the jobs. One jobexecutor tries to lock a job, and another tries this also. After acquiring the lock, they can execute it. But in this acquire phase you can expect to see the stale exceptions ...

This doesn't mean that there is something wrong. The JobExecutor is aware of these StaleExceptions and will act accordingly (ie leave the job alone for that moment). Unfortunately, this logrecord is created by Hibernate, which makes it hard to write code that doesn't throw this exception (if it is even possible)

[sshetty]

So is the message harmless and can be ignored ?