Menu ▾ ▴

Connection leak issues

Help
Sumit
2015-09-21
2015-10-27

  • Sumit

    Sumit - 2015-09-21

    We are using ha-jdbc 2.0.16, and we are seeing following statements in the log files

    DBCP object created at XXXXXX by the following code was never closed
    at org.apache.tomcat.dbcp.dbcp.AbandonedTrace.setStackTrace(AbandonedTrace.java:139)
    at org.apache.tomcat.dbcp.dbcp.AbandonedObjectPool.borrowObject(AbandonedObjectPool.java:81)
    at org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
    at org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider.getConnection(InjectedDataSourceConnectionProvider.java:71)
    at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:446)
    at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:167)
    at org.hibernate.jdbc.JDBCContext.connection(JDBCContext.java:142)
    at org.hibernate.transaction.JDBCTransaction.begin(JDBCTransaction.java:85)
    at org.hibernate.impl.SessionImpl.beginTransaction(SessionImpl.java:1463)
    at org.hibernate.ejb.TransactionImpl.begin(TransactionImpl.java:60)

    What does this represent and how to resolve this?

    Thanks for your help in advance.

    Regards,
    Sumit

     

  • Paul Ferraro

    Paul Ferraro - 2015-10-27

    Sorry for the slow response. Have you figured this out yet?
    I don't see HA-JDBC anywhere in this stacktrace - why do you suppose that HA-JDBC is the source of the unclosed connection?

     

Log in to post a comment.