Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by monktastic
, 1 year ago
Apparent connection leak detected
java.lang.Exception: Apparent connection leak detected at slick.jdbc.hikaricp.HikariCPJdbcDataSource.createConnection(HikariCPJdbcDataSource.scala:12) at slick.jdbc.JdbcBackend$BaseSession.conn$lzycompute(JdbcBackend.scala:415) at slick.jdbc.JdbcBackend$BaseSession.conn(JdbcBackend.scala:414) at slick.jdbc.JdbcBackend$SessionDef$class.prepareStatement(JdbcBackend.scala:297) at slick.jdbc.JdbcBackend$BaseSession.prepareStatement(JdbcBackend.scala:407) at slick.jdbc.StatementInvoker.results(StatementInvoker.scala:33) at slick.jdbc.StatementInvoker.iteratorTo(StatementInvoker.scala:22) at slick.jdbc.StreamingInvokerAction$class.emitStream(StreamingInvokerAction.scala:28) at slick.driver.JdbcActionComponent$QueryActionExtensionMethodsImpl$$anon$1.emitStream(JdbcActionComponent.scala:218) at slick.driver.JdbcActionComponent$QueryActionExtensionMethodsImpl$$anon$1.emitStream(JdbcActionComponent.scala:218) at slick.backend.DatabaseComponent$DatabaseDef$$anon$3.run(DatabaseComponent.scala:285) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)