[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-360) WebLogic DataSource doesn't permit conn.getWarnings after commit

[<leg...@at...>]

The following comment has been added to this issue:

     Author: CVS Notification Service
    Created: Tue, 20 Jan 2004 8:38 AM
       Body:
CVS COMMIT LOG: 
SUBJECT: [Hibernate-commits] Hibernate2/src/net/sf/hibernate/impl BatcherImpl.java,1.9.2.16,1.9.2.17
applied HB-360, workaround for weblogic bad behavior (John Kristian)


---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-360


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-360
    Summary: WebLogic DataSource doesn't permit conn.getWarnings after commit
       Type: Patch

     Status: Closed
   Priority: Major
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1.2
   Versions:
             2.0.2

   Assignee: Gavin King
   Reporter: John Kristian

    Created: Wed, 24 Sep 2003 1:49 PM
    Updated: Tue, 20 Jan 2004 8:38 AM
Environment: WebLogic 7, Windows 2000, Microsoft SQL Server

Description:
SessionFactoryImpl.closeConnection fails to close the JDBC conection, because an exception propagates from conn.getWarnings, because the connection is already closed (as a side-effect of commiting the JTA transaction, I suppose).  This patch solves the problem:

==== src/net/sf/hibernate/impl/SessionFactoryImpl.java ====
@@ -403,6 +403,11 @@
 		try {
 			JDBCExceptionReporter.logWarnings( conn.getWarnings() );
 			conn.clearWarnings();
+		}
+		catch (SQLException sqle) {
+			log.warn("Cannot log warnings: " + sqle.getMessage());
+		}
+		try {
 			connections.closeConnection(conn);
 		}
 		catch (SQLException sqle) {



---------------------------------------------------------------------
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