Comment 22 for bug 1243551

Getting this also in production on 0.8.1-SNAPSHOT with disableConnectionTracking set to true.

1) Shutdown Play app.
2) Restart MySQL
3) Start Play app.

So we have 2 freshly started services, and yet within 30 minutes of starting play app, Fatal error, "No operations allowed after connection closed" followed by same error randomly from there on out, in bunches, or singly.

@wwadge
> If for some reason the idle test connection function is not working right, the pool ends up with a connection that it thinks is ok, but one which the server has closed off and thus blows up.

That the error occurs well before the 8 hour MySQL idle timeout would seem to indicate that the problem lies elsewhere, no?