SBT not releasing connection pool when recompiling

24 views

Skip to first unread message

Larry Simon

unread,

Aug 23, 2016, 12:00:22 PM8/23/16

to Slick / ScalaQuery

Using Slick 3.1, Play 2.4 and latest SBT with MySQL we've found that every time we change the application source code, and SBT automatically recompiles the app, another 20 database connections gets added (i.e. the old ones aren't released). Anyone have some insight? Bug in SBT or Slick?

Victor Para

unread,

Oct 14, 2016, 6:42:31 PM10/14/16

to Slick / ScalaQuery

Make sure the database closes when the application shuts down. If the connection persists while the entire JVM is still alive then you get those issues. probably you are using the database in embedded mode ?

Larry Simon

unread,

Oct 14, 2016, 7:31:21 PM10/14/16

to Slick / ScalaQuery

It turned out to be an issue with Play 2.4 that was fixed in Play 2.5.

Reply all

Reply to author

Forward

0 new messages