swaldman/c3p0 issues and pull requests

#85 - Typo in log: conection resource close

Issue - State: closed - Opened by ChargingBulle about 8 years ago

#84 - DEADLOCK with C3P0 on java se application

Issue - State: closed - Opened by TheSkay about 8 years ago - 1 comment

#83 - Application acquires high number of connections on boot time

Issue - State: closed - Opened by ahmednasir91 about 8 years ago - 5 comments

#82 - An unexpected error occured caused by exception PersistenceException: org.hibernate.exception.GenericJDBCException: Cannot open connection

Issue - State: open - Opened by ghost about 8 years ago - 2 comments

#81 - Sptingboot running error

Issue - State: open - Opened by ahmetkarakaya about 8 years ago

#80 - c3p0 produce java.lang.RuntimeException: Internal inconsistency: A (not new) checking-out statement is not in deathmarch.

Issue - State: open - Opened by levyfan over 8 years ago - 1 comment

#79 - Resource pool not waiting on destroyer threads

Issue - State: open - Opened by bgedik over 8 years ago - 2 comments

#76 - Specify a custom Executor to run background threads

Issue - State: closed - Opened by ghost over 8 years ago - 3 comments

#72 - Properties configuration file problem

Issue - State: closed - Opened by Nips almost 9 years ago - 6 comments

#68 - Contribution

Issue - State: closed - Opened by genrym almost 9 years ago - 3 comments

#65 - Creating more connections in the pool than needed?

Issue - State: open - Opened by mhisoft almost 9 years ago - 5 comments

#61 - Possible memory leak in c3p0 in Hibernate?

Issue - State: open - Opened by xzhang27 about 9 years ago - 7 comments

#59 - Bug #133: guard protecting C3P0 from drivers not proxying statements correctly.

Pull Request - State: closed - Opened by t-beckmann over 9 years ago - 1 comment

#57 - Java 8 required

Issue - State: closed - Opened by rotty3000 over 9 years ago - 5 comments

#53 - c3p0-0.9.1.2 APPARENT DEADLOCK!!

Issue - State: closed - Opened by yamadakin almost 10 years ago - 6 comments

#47 - Any error in Postgres transaction causes C3P0 to close connections

Issue - State: closed - Opened by radaczynski almost 10 years ago - 10 comments

#41 - C3P0 should allow use of injected Executor

Issue - State: closed - Opened by mrossi975 about 10 years ago - 2 comments

#37 - InterruptedException is wrapped within an SQLException in C3P0PooledConnection

Issue - State: closed - Opened by robertverdes over 10 years ago - 1 comment

#34 - c3p0 produces java.sql.SQLWarning: 010CP: AutoCommit option has changed to true. All pending statements on this transaction (if any) are committed.

Issue - State: closed - Opened by makhomed over 10 years ago

#30 - Cancel statements before closing when destroying unreturned connection after timeout

Pull Request - State: open - Opened by adangel over 10 years ago - 4 comments

#26 - how to deregister JDBC driver to prevent a memory leak?

Issue - State: closed - Opened by makhomed over 10 years ago

#24 - initialPoolSize configuration doen't work in tomcat

Issue - State: open - Opened by ihepda almost 11 years ago - 2 comments

#22 - C3p0 0.9.5 pre7.spectral

Pull Request - State: closed - Opened by mffrench almost 11 years ago - 6 comments

#20 - "A client timed out while waiting to acquire a resource from com.mchange.v2.resourcepool.BasicResourcePool@f03f0af -- timeout at awaitAvailable()"

Issue - State: open - Opened by tazmaniax almost 11 years ago - 18 comments

#18 - c3p0 0.9.2.1 - java.lang.AbstractMethodError: com.mchange.v2.c3p0.impl.NewProxyResultSet.isClosed()

Issue - State: closed - Opened by kappolo over 11 years ago - 17 comments

#6 - The connection is closed Exception

Issue - State: closed - Opened by bianjiang almost 12 years ago - 4 comments

Ecosyste.ms: Issues

GitHub / swaldman/c3p0 issues and pull requests