[
http://jira.jboss.com/jira/browse/HIBERNATE-12?page=comments#action_12316746 ]
Stephen Pearson commented on HIBERNATE-12:
--
Thanks for your feedback Steve.
Currently I am using a modified version of the TransactionSync class, which
does close the JDBC connection, and this works quite well.
Can't wait to see how JBoss 4.02 and hibernate 3 will improve my application.
HibernateContext JDBC Connection
Key: HIBERNATE-12
URL: http://jira.jboss.com/jira/browse/HIBERNATE-12
Project: Hibernate
Type: Bug
Environment: Mac OSX, JBoss 4.01sp1
Reporter: Stephen Pearson
Assignee: Steve Ebersole
Original Estimate: 1 hour
Remaining: 1 hour
When using the HibernateContext getSession() function call, all works well
until the function call has finished, and then the underlying JDBC connection
is not closed. Therefore with each call to getSession within my EJB I
promptly receieve a Closing a connection for you. Please close them
yourself. warning from the CachedConnectionManager.
Can the TransactionSynch call please close the JDBC connection when it
flushes and closes the Hibernate Session.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
