-->
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: How can CMT work with aggressive release mode
PostPosted: Fri Jan 23, 2009 8:43 am 
Newbie

Joined: Fri Jan 23, 2009 8:30 am
Posts: 2
A question regarding Container Managed Connections:

Hibernate docs (chapter 11.5) state that hibernate.connection.release_mode should not be set to after_transaction when using JTA. Indeed looking through the source, when using the CMTTransactionFactory the release_mode defaults to after_statement.

My question is, how can a transaction continue over several connections (as will happen with an aggressive release strategy) when not using an XA datasource? Surely the closing of the connection will commit the transaction and mean that it will not be possible to roll the transaction back as a whole.

As such, I would prefer to use after_transaction for my release mode, however the documentation states that this should not be used. Any ideas as to why this would be?
Thanks


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.