BoneCP 0.8.0-release erroneously detecting unclosed connections & closing them
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BoneCP |
New
|
Undecided
|
Unassigned |
Bug Description
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
2013-12-09 10:41:56,644 : WARN : com.jolbox.
2013-12-09 10:41:56,722 : ERROR : com.XXX.
com.mysql.
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: /groups. google. com/forum/ #!topic/ play-framework/ eshzvWuNQcc
https:/