Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 25 Sep 2003 4:24 PM
I fixed this in CVS
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-337
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-337
Summary: Connections from DataSource + WebSphere
Type: Task
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 beta 4
Versions:
2.0 final
2.0.1
2.0.2
2.0.3
Assignee:
Reporter: Ralf Taugerbeck
Created: Tue, 16 Sep 2003 7:20 AM
Updated: Thu, 25 Sep 2003 4:24 PM
Environment: Hibernate configured with DataSources on WebSphere
Description:
Using Hibernate 2.0.x with Datasource connections on WebSphere (4.0, 5.0) the following error message occurs when closing a Hibernate Session:
net.sf.hibernate.util.JDBCExceptionReporter TRAS0014I: The following exception was logged com.ibm.websphere.ce.cm.StaleConnectionException: Connection is closed
WebSphere seems to close the connection after a UserTransaction#commit but Hibernate afterwards in SessionFactoryImpl#closeConnection tries to call #getWarnings on the closed connection which causes the above exception.
----
The behavior can be fixed by either checking for closed connections in SessionFactoryImpl#closeConnection or by configuring the data source to "Disable auto connection cleanup" (checkbox in the data source setup in Websphere) -> FAQ
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
