[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-1240) Track connection leakage in JDBCContext.afterTransactionCompletion()
Steve Ebersole (JIRA)
noreply at atlassian.com
Mon Mar 21 13:00:39 EDT 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Ebersole closed HHH-1240.
-------------------------------
Closing stale resolved issues
> Track connection leakage in JDBCContext.afterTransactionCompletion()
> --------------------------------------------------------------------
>
> Key: HHH-1240
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1240
> Project: Hibernate Core
> Issue Type: Bug
> Components: core
> Reporter: Gavin King
> Assignee: Steve Ebersole
> Priority: Critical
> Fix For: 3.1
>
>
> Currently we detect connection leakages using a finalizer on ConnectionManager, and in aggressiveRelease().
> It would be MUCH better if we did this stuff in afterCompletion phase, now that we don't usually hold onto connections between txns.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list