BoneCP 0.8.0-release erroneously detecting unclosed connections & closing them

[Jeffrey Schmidt]

I've been using BoneCP 0.7.1-release on a very high-traffic transactional application for a while, and I recently tried upgrading to 0.8.0-release. Since the upgrade, I've consistently been getting 'BoneCP detected an unclosed connection...' errors (see below). I'm using MySQL with the latest JDBC driver and plain JDBC (no hibernate, etc). The only non-default BoneCP settings that I'm using are max_connections=5000 & enable_statistics=true. I can reliably reproduce this issue when I run my program, but the only real thing that seems to trigger this behavior is that I have a lot of connections open & active. I have reverted to 0.7.1-release for now.

2013-12-09 10:41:56,644 : WARN : com.jolbox.bonecp.ConnectionPartition:162 : BoneCP detected an unclosed connection and will now attempt to close it for you. You should be closing this connection in your application - enable connectionWatch for additional debugging assistance or set disableConnectionTracking to true to disable this feature entirely.
2013-12-09 10:41:56,722 : ERROR : com.XXX.XXX.database.DatabaseInterface:435 : com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after connection closed.
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after connection closed.

[Nikita (mr-niko)]

I confirm that. We encounter the same problem with 0.8.0-release and PostgreSQL 9.2.6.
Near 2-3 log records per day: BoneCP detected an unclosed connection and will now attempt to close it for you.

Also, take a look here, play framework users faced with this too:
https://groups.google.com/forum/#!topic/play-framework/eshzvWuNQcc

[KwonNam Son (kwon37xi)]

I had the same problem with bonecp 0.8 RELEASE.
I could avoid the problem with the following setting.

boneCpDataSource.setDisableConnectionTracking(true);