-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: Optimistic Lock using auto_close_session and CMT
PostPosted: Tue Jun 28, 2005 3:24 am 
Beginner
Beginner

Joined: Sun Mar 28, 2004 9:01 am
Posts: 21
Hello,

I'm having problem with the Automatic JTA and Session binding in Hibernate 3 and the optimistic lock strategy.

If I update a row the version number get's incremented only after the transaction commits. The commit occurs on transaction completion, that is after the EJB returns. As we use the DTO patterns, the value of the version attribute is copied before the transaction commits thus we have an old value. The next time we want to update Hibernate throws an org.hibernate.StaleObjectStateException.

I use the following configuration options:

hibernate.transaction.auto_close_session=true
hibernate.transaction.flush_before_completion=true

Any ideas how to handle the problem other than loading the Object for a second time in the web tier?

thx
Rene

Hibernate version: 3.0.4


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.