[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-1445) SchemaUpdate closes shared ConnectionProvider
Steve Ebersole (JIRA)
noreply at atlassian.com
Mon Mar 21 13:01:10 EDT 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Ebersole closed HHH-1445.
-------------------------------
Closing stale resolved issues
> SchemaUpdate closes shared ConnectionProvider
> ---------------------------------------------
>
> Key: HHH-1445
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1445
> Project: Hibernate Core
> Issue Type: Bug
> Components: core
> Affects Versions: 3.1.2
> Reporter: fdo
> Assignee: Steve Ebersole
> Fix For: 3.2.0.alpha1, 3.1.3
>
>
> Summary of thread : http://forum.hibernate.org/viewtopic.php?p=2289756
> - I have a standalone application, configured to use c3p0 as connection pool
> - when I first connect to the db, Hibernate updates the database using SchemaUpdate from SessionFactoryImpl. This schema update is created using the SchemaUpdate(cfg, settings) constructor [[this constructor didn't exist in Hibernate 3.0.5 but it does in 3.1.2]], which doesn't instantiate a new ConnectionProvider but uses the one from the settings
> - when SchemaUpdate is done, it closes the ConnectionProvider, which cannot be used afterwards
> - afterwards, when I try to do something on the database, it appears the (closed) connection provider from the settings is used and it explodes...
--
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