[jboss-user] [JBossCache] - Re: Optimistic DataVersioningException on read-only objects

hargitt do-not-reply at jboss.com
Thu Feb 15 09:49:25 EST 2007


Hi,

We are having a similar problem with Optimistic locking in JbossCache 1.4.1.SP1 together with Hibernate 3.2.2 on JBoss 4.0.4.GA. 

Whenever we commit a trasaction, we are seeing a harmless (it seems) warning:
WARN  [TreeCache] status is 3 (not ACTIVE or PREPARING); returning null)

Futher more, when we are updating two or more different objects simultaneously (same class) we get a versioning exception:

2007-02-15 16:12:01,563 ERROR [org.jboss.ejb.plugins.LogInterceptor] RuntimeException in method: public abstract void com.upstreamsystems.mip.clubs.EJB.hibernateslsb.HClubManager.setMemberVariables(java.lang.Long,java.util.Map) throws java.rmi.RemoteException:
  | 
  | org.hibernate.TransactionException: JTA commit failed: 
  | 
  | 	at org.hibernate.transaction.JTATransaction.commit(JTATransaction.java:153)
  | ...
  | Caused by: org.jboss.tm.JBossRollbackException: Unable to commit, tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=traviata/299, BranchQual=, localId=299] status=STATUS_NO_TRANSACTION; - nested throwable: (java.lang.RuntimeException: )
  | 
  | 	at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:372)
  | 
  | 	at org.jboss.tm.TxManager.commit(TxManager.java:240)
  | 
  | 	at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:140)
  | 
  | 	at org.hibernate.transaction.JTATransaction.commit(JTATransaction.java:146)
  | 
  | 	... 50 more
  | 
  | Caused by: java.lang.RuntimeException: 
  | 
  | 	at org.jboss.cache.interceptors.TxInterceptor$LocalSynchronizationHandler.beforeCompletion(TxInterceptor.java:1148)
  | 
  | 	at org.jboss.cache.interceptors.OrderedSynchronizationHandler.beforeCompletion(OrderedSynchronizationHandler.java:75)
  | 
  | 	at org.jboss.tm.TransactionImpl.doBeforeCompletion(TransactionImpl.java:1491)
  | 
  | 	at org.jboss.tm.TransactionImpl.beforePrepare(TransactionImpl.java:1110)
  | 
  | 	at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:324)
  | 
  | 	... 53 more
  | 
  | Caused by: org.jboss.cache.optimistic.DataVersioningException: DataNode [/com/upstreamsystems/mip/clubs/VO/Impl/ClbMemberVariable] version Ver=31 is newer than workspace node Ver=30
  | 
  | 	at org.jboss.cache.interceptors.OptimisticValidatorInterceptor.simpleValidate(OptimisticValidatorInterceptor.java:147)
  | 
  | 	at org.jboss.cache.interceptors.OptimisticValidatorInterceptor.validateNodes(OptimisticValidatorInterceptor.java:110)
  | 
  | 	at org.jboss.cache.interceptors.OptimisticValidatorInterceptor.invoke(OptimisticValidatorInterceptor.java:75)
  | 
  | 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
  | 
  | 	at org.jboss.cache.interceptors.OptimisticLockingInterceptor.invoke(OptimisticLockingInterceptor.java:99)
  | 
  | 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
  | 
  | 	at org.jboss.cache.interceptors.TxInterceptor.runPreparePhase(TxInterceptor.java:861)
  | 
  | 	at org.jboss.cache.interceptors.TxInterceptor$LocalSynchronizationHandler.beforeCompletion(TxInterceptor.java:1126)
  | 
  | 	... 57 more

If we run everything under one thread, then then error does not occur. 

I am trying to join this experience with forum entry: http://jboss.org/index.html?module=bb&op=viewtopic&t=92818&postdays=0&postorder=asc&start=30 but if I go back to 1.3.0.SP2 I start getting the null pointer exception bug that was fixed in the next release. 

Any Ideas?


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017059#4017059

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017059



More information about the jboss-user mailing list