an attempt to checkout a resource was interrupted, and the pool is still live: some other thread must have either interrupted the Thread attempting checkout!

[Odd Vinje]

Getting this and after a short while, confluence responds with a 505. After 10-15 mins it responds ok again.

Seems related to usage of C3P0

This has now happened a few times last few days.

Anyone who knows what causes this error? We are using postgres as database server on a different node.

[Mike Rocheleau]

We get this as well, Confluence 5.1.5 - we see our tomcat threads spike to whatever our maxthreads is set to at the time (tried between 150 and 1000), and database connections are pinned at maximum then too (tried between 30 and 100).

It goes away after a while, it could return though, we've had it for maybe a couple of months off and on, sometimes more than others.

No idea what's really causing it yet...

[Andy Ukasick]

Hi.  Did you ever figure out what was causing this?  We also are experiencing this.  We use an Oracle db.  We're not allowed to run Confluence as root so we have 'iptables' configured to redirect ports 80/443 to 8080/8443.  Confluence is listening on 8080 and 8443, not 8090 and 8443.  

There are indications that the db driver does a reverse lookup on itself whenever attempting to open a db connection and sometimes it chokes at that point (maybe no response or response takes too long? Or??).  Whatever the root cause, during periods of high activity we will start getting interrupted thread errors in the resource pool (C3P0) and DEADLOCK thread errors.  It eventually clears, but while it happens, Confluence just hangs and hangs.