Hi,
regarding http://forum.hibernate.org/viewtopic.php?t=945497&highlight=
I would like to ask the forum again what is the sense of
configuration setting. The documentation says that Hibernate will release the JDBC connection after each statement execution and this is the suggested strategy to use in a JTA environment. Why? Why should the connection be released after statement execution and not at the end of a transaction? And what happens with the connection obtained via session.connection() call when this setting is used? Is the app code responsible for the connection close?
It would be really helpful to us to know your opinion. We have to find out whether it's a WebLogic problem or not (see http://forum.hibernate.org/viewtopic.php?t=945497&highlight=).

Best regards,
Sergiy

Because JTA does not call beforeTransactionCompletion() if the transaction is being rolled back, and so there would be no chance to close the connection.



I must admit I never really thought about it. I assumed that in a CMT/JCA environment, you just obtain the connection the normal way via the Datasource. JCA guarantees it is the same underlying connection Hibernate is using.

However, I can see in your other post that if you do get the Connection via Session.connection(), you have a problem releasing it. We'll have to change the impl of Session.connection() when release_mode=after_statement.

The workaround, of course, is to get the connection in the standard J2EE way....

Fixed in CVS. Note that it is the application's responsibility to call connection.close().

Thanks a lot Gavin! I thank you really very much.

...just one remark: it would make sense to put the comment about the app responsibility to close the connection into the API documentation for Session.connection() method.