I also get this problem with Play Framework 2.1.4, mySQL.
Has anybody found a definitive solution? For the moment, I do the following:
* Wrote some code in Global.scala to take into account the setDisableConnectionTracking=true
* Use the 0.8.0-RELEASE version
* Use the following DB config:
db.default.partitionCount=1
db.default.maxConnectionsPerPartition=7
db.default.minConnectionsPerPartition=7
db.default.acquireIncrement=1
db.default.acquireRetryAttempts=1
db.default.acquireRetryDelay=5 seconds
db.default.connectionTimeout=30 seconds
db.default.idleMaxAge=1 minutes
db.default.idleConnectionTestPeriod=30 seconds
db.default.connectionTestStatement="SELECT 1"
db.default.maxConnectionAge=0
db.default.autoReconnect=true
I haven't seen the bug anymore for a few hours but I am not totally sure it is fixed with this.
I also get this problem with Play Framework 2.1.4, mySQL.
Has anybody found a definitive solution? For the moment, I do the following:
* Wrote some code in Global.scala to take into account the setDisableConne ctionTracking= true partitionCount= 1 maxConnectionsP erPartition= 7 minConnectionsP erPartition= 7 acquireIncremen t=1 acquireRetryAtt empts=1 acquireRetryDel ay=5 seconds connectionTimeo ut=30 seconds idleMaxAge= 1 minutes idleConnectionT estPeriod= 30 seconds connectionTestS tatement= "SELECT 1" maxConnectionAg e=0 autoReconnect= true
* Use the 0.8.0-RELEASE version
* Use the following DB config:
db.default.
db.default.
db.default.
db.default.
db.default.
db.default.
db.default.
db.default.
db.default.
db.default.
db.default.
db.default.
I haven't seen the bug anymore for a few hours but I am not totally sure it is fixed with this.