com.ibm.db2.jcc.b.SqlException: ... java.sql.Connextion.close() requested while a transaction is in progress on the connection. The transaction remains active, and the connection cannot be closed. ERRORCODE=-4471, SQLSTATE=null ... // obfuscated calls from com.ibm.db2.jcc.b.*

Hibernate JIRA | Julien Kronegg | 7 years ago
  1. 0

    When doing a hbm2java ant task to generate entities from the database, an exception occurs when closing the connection pool if transactions are used. INFO: cleaning up connection pool: jdbc:db2://192.168.17.12:8801/TES1 org.hibernate.connection.DriverManagerConnectionProvider close WARNING: problem closing pooled connection Throwable occured: com.ibm.db2.jcc.b.SqlException: ... java.sql.Connextion.close() requested while a transaction is in progress on the connection. The transaction remains active, and the connection cannot be closed. ERRORCODE=-4471, SQLSTATE=null ... // obfuscated calls from com.ibm.db2.jcc.b.* at org.ibm.db2.jcc.b.jb.close(jb.java:1089) at org.hibernate.connection.DriverManagerConnectionProvider.close(DriverManagerConnectionProvider:175) at org.hibernate.cfg.JDBCBinder.readFromDatabase(JDBCBinder:95) ... at org.hibernate.tool.ant.Hbm2JavaExporterTask.configureExporter(Hbm2JavaExporterTask:43) This is only a warning and the hbm2java ant task do the Java file generation correctly. However, this warning make think about a problem when generating the entities from the database. The solution may be to commit/rollback the transaction (if any) before closing the connection pool. This could be done in JDBCBinder.readFromDatabase() or in the DriverManagerConnectionProvider.close() methods. Workaround: ----------------- Set the following property in the hibernate properties file used for the ant task: hibernate.connection.autocommit=true

    Hibernate JIRA | 7 years ago | Julien Kronegg
    com.ibm.db2.jcc.b.SqlException: ... java.sql.Connextion.close() requested while a transaction is in progress on the connection. The transaction remains active, and the connection cannot be closed. ERRORCODE=-4471, SQLSTATE=null ... // obfuscated calls from com.ibm.db2.jcc.b.*
  2. 0

    When doing a hbm2java ant task to generate entities from the database, an exception occurs when closing the connection pool if transactions are used. INFO: cleaning up connection pool: jdbc:db2://192.168.17.12:8801/TES1 org.hibernate.connection.DriverManagerConnectionProvider close WARNING: problem closing pooled connection Throwable occured: com.ibm.db2.jcc.b.SqlException: ... java.sql.Connextion.close() requested while a transaction is in progress on the connection. The transaction remains active, and the connection cannot be closed. ERRORCODE=-4471, SQLSTATE=null ... // obfuscated calls from com.ibm.db2.jcc.b.* at org.ibm.db2.jcc.b.jb.close(jb.java:1089) at org.hibernate.connection.DriverManagerConnectionProvider.close(DriverManagerConnectionProvider:175) at org.hibernate.cfg.JDBCBinder.readFromDatabase(JDBCBinder:95) ... at org.hibernate.tool.ant.Hbm2JavaExporterTask.configureExporter(Hbm2JavaExporterTask:43) This is only a warning and the hbm2java ant task do the Java file generation correctly. However, this warning make think about a problem when generating the entities from the database. The solution may be to commit/rollback the transaction (if any) before closing the connection pool. This could be done in JDBCBinder.readFromDatabase() or in the DriverManagerConnectionProvider.close() methods. Workaround: ----------------- Set the following property in the hibernate properties file used for the ant task: hibernate.connection.autocommit=true

    Hibernate JIRA | 7 years ago | Julien Kronegg
    com.ibm.db2.jcc.b.SqlException: ... java.sql.Connextion.close() requested while a transaction is in progress on the connection. The transaction remains active, and the connection cannot be closed. ERRORCODE=-4471, SQLSTATE=null ... // obfuscated calls from com.ibm.db2.jcc.b.*
  3. 0

    Atricore_文档搜索

    anggang.com | 11 months ago
    com.ibm.db2.jcc.b.SqlException: [jcc][t4][10251][10308][3.50.152] java.sql.Connection.close() requested while a transaction is in progress on the connection. The transaction remains active, and the connection cannot be closed. ERRORCODE=-4471, SQLSTATE=null
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Problem creating dataset using db2 stored proce... | Oracle Community

    oracle.com | 1 year ago
    com.ibm.db2.jcc.b.SqlException: [jcc][10120][10943][3.50.152] Invalid operation: statement is closed. ERRORCODE=-4470, SQLSTATE=null
  6. 0

    java blob to byte array conversion error issue

    Stack Overflow | 3 years ago | user3497393
    com.ibm.db2.jcc.b.SqlException: [jcc][10120][11936][3.50.152] Invalid operation: Lob is closed. ERRORCODE=-4470, SQLSTATE=null

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.ibm.db2.jcc.b.SqlException

      ... java.sql.Connextion.close() requested while a transaction is in progress on the connection. The transaction remains active, and the connection cannot be closed. ERRORCODE=-4471, SQLSTATE=null ... // obfuscated calls from com.ibm.db2.jcc.b.*

      at org.ibm.db2.jcc.b.jb.close()
    2. org.ibm.db2
      jb.close
      1. org.ibm.db2.jcc.b.jb.close(jb.java:1089)
      1 frame
    3. Hibernate
      DriverManagerConnectionProvider.close
      1. org.hibernate.connection.DriverManagerConnectionProvider.close(DriverManagerConnectionProvider:175)
      1 frame
    4. Hibernate
      JDBCBinder.readFromDatabase
      1. org.hibernate.cfg.JDBCBinder.readFromDatabase(JDBCBinder:95)
      1 frame