Called: java.sql.SQLException: JDBC4 Connection.isValid () method is not supported

Question

My game board project works well in my local, but when I try to deploy it to heroku, I get the following error.

2015-07-05T06:24:10.456657+00:00 app[web.1]: at com.google.inject.Guice.createInjector(Guice.java:73) 2015-07-05T06:24:10.456817+00:00 app[web.1]: at play.api.inject.guice.GuiceApplicationBuilder.build(GuiceApplicationBuilder.scala:93) 2015-07-05T06:24:10.456702+00:00 app[web.1]: at com.google.inject.Guice.createInjector(Guice.java:62) 2015-07-05T06:24:10.456746+00:00 app[web.1]: at play.api.inject.guice.GuiceBuilder.injector(GuiceInjectorBuilder.scala:126) 2015-07-05T06:24:10.456863+00:00 app[web.1]: at play.api.inject.guice.GuiceApplicationLoader.load(GuiceApplicationLoader.scala:21) 2015-07-05T06:24:10.456909+00:00 app[web.1]: at play.core.server.ProdServerStart$.start(ProdServerStart.scala:52) 2015-07-05T06:24:10.456951+00:00 app[web.1]: at play.core.server.ProdServerStart$.main(ProdServerStart.scala:27) 2015-07-05T06:24:10.456994+00:00 app[web.1]: at play.core.server.ProdServerStart.main(ProdServerStart.scala) 2015-07-05T06:24:10.457407+00:00 app[web.1]: at com.zaxxer.hikari.pool.BaseHikariPool.addConnection(BaseHikariPool.java:441) 2015-07-05T06:24:10.457496+00:00 app[web.1]: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 2015-07-05T06:24:10.457369+00:00 app[web.1]: Caused by: java.sql.SQLException: JDBC4 Connection.isValid() method not supported, connection test query must be configured 2015-07-05T06:24:10.457602+00:00 app[web.1]: at java.util.concurrent.FutureTask.run(FutureTask.java:266) 2015-07-05T06:24:10.457451+00:00 app[web.1]: at com.zaxxer.hikari.pool.BaseHikariPool$1.run(BaseHikariPool.java:413) 2015-07-05T06:24:10.457681+00:00 app[web.1]: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 2015-07-05T06:24:10.457812+00:00 app[web.1]: at java.lang.Thread.run(Thread.java:745) 2015-07-05T06:24:10.457768+00:00 app[web.1]: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 2015-07-05T06:24:11.231007+00:00 heroku[web.1]: Process exited with status 255 2015-07-05T06:24:11.243795+00:00 heroku[web.1]: State changed from starting to crashed 2015-07-05T06:24:11.245013+00:00 heroku[web.1]: State changed from crashed to starting 2015-07-05T06:24:16.259302+00:00 heroku[web.1]: Starting process with command `target/universal/stage/bin/sazors -Dhttp.port=10803` 2015-07-05T06:24:17.542815+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -Xmx384m -Xss512k -Dfile.encoding=UTF-8 2015-07-05T06:24:18.643391+00:00 app[web.1]: 06:24:18,391 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy] 2015-07-05T06:24:18.643397+00:00 app[web.1]: 06:24:18,391 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] 

I am using PostgreSQL as my db and slick as a database access library. I tried to do this, and after some research it turned out that this error can be caused if the specified URL in the configuration file is incorrect or it returns null. I tried to fix it, but I could not resolve this error.

Here is my Procfile:

web: target / universal / stage / bin / myapp -Dhttp.port = $ {PORT} -Dconfig.resource = $ {PLAY_CONF_FILE}

and Application.conf

 slick.dbs.default.driver="slick.driver.PostgresDriver$" slick.dbs.default.db.driver="org.postgresql.Driver" slick.dbs.default.db.url="postgres://rycmvicwkkzofh: [e-mail] s.com:5432/d5pr4h65obtb0s" slick.dbs.default.db.user=rycmuicwkkzofh slick.dbs.default.db.password="copiedfromheroku" 

PS: I am working on these versions

play framework version : 2.4.0 slick version : 3.0

EDIT : if I add slick.dbs.default.db.connectionTestQuery="SELECT 1" to my application.conf file, you will get a new error type nullPointerException.

 That is gone but getting new error now: 2015-07-05T12:22:49.781133+00:00 app[web.1]: at com.google.inject.Guice.createInjector(Guice.java:73) 2015-07-05T12:22:49.781201+00:00 app[web.1]: at com.google.inject.Guice.createInjector(Guice.java:62) 2015-07-05T12:22:49.781283+00:00 app[web.1]: at play.api.inject.guice.GuiceBuilder.injector(GuiceInjectorBuilder.scala:126) 2015-07-05T12:22:49.781361+00:00 app[web.1]: at play.api.inject.guice.GuiceApplicationBuilder.build(GuiceApplicationBuilder.scala:93) 2015-07-05T12:22:49.781507+00:00 app[web.1]: at play.core.server.ProdServerStart$.start(ProdServerStart.scala:52) 2015-07-05T12:22:49.781425+00:00 app[web.1]: at play.api.inject.guice.GuiceApplicationLoader.load(GuiceApplicationLoader.scala:21) 2015-07-05T12:22:49.781599+00:00 app[web.1]: at play.core.server.ProdServerStart$.main(ProdServerStart.scala:27) 2015-07-05T12:22:49.781669+00:00 app[web.1]: at play.core.server.ProdServerStart.main(ProdServerStart.scala) 2015-07-05T12:22:49.782161+00:00 app[web.1]: Caused by: java.lang.NullPointerException 2015-07-05T12:22:49.782226+00:00 app[web.1]: at com.zaxxer.hikari.pool.BaseHikariPool.addConnection(BaseHikariPool.java:446) 2015-07-05T12:22:49.782328+00:00 app[web.1]: at com.zaxxer.hikari.pool.BaseHikariPool$1.run(BaseHikariPool.java:413) 2015-07-05T12:22:49.782417+00:00 app[web.1]: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 2015-07-05T12:22:49.782515+00:00 app[web.1]: at java.util.concurrent.FutureTask.run(FutureTask.java:266) 2015-07-05T12:22:49.783691+00:00 app[web.1]: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 2015-07-05T12:22:49.783803+00:00 app[web.1]: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 2015-07-05T12:22:49.783883+00:00 app[web.1]: at java.lang.Thread.run(Thread.java:745) 

Answer 1

I believe this issue was discussed on the Play mailing list here .

The reason was that Slick does not support the DATABASE_URL format that Heroku sets. You need to parse DATABASE_URL into the JDBC URL. You can do this quite easily with the heroku-jdbc library: https://github.com/jkutner/heroku-jdbc

Just add this line to your folders:

 libraryDependencies += "com.heroku.sdk" % "heroku-jdbc" % "0.1.0" 

Then you can parse the url like this:

 var jdbcURL = DatabaseUrl.extract.jdbcUrl 

Then pass this url to delete

EDIT

In fact, most people seem to parse DATABASE_URL manually and adjust the hardcoded values ​​for the snapshot. This is great, but keep in mind that the connection may change and you will have to manually change the settings.

So, you need to change your config to this:

 slick.dbs.default.db.url="jdbc:postgresql://host:port/path" 

But you may want to destroy and recreate your database because you posted information about your connection publicly.

I published a PR to fix this: https://github.com/slick/slick/pull/1193

Answer 2

The Play HikariCP module (find the configuration "connectionTestQuery") offers to set up a test query as follows:

 slick.dbs.default.db.connectionTestQuery="/*ping*/ select 1" // or whatever 

Then the error in your stack should theoretically go away.

Answer 3

To configure playback, you must use the jdbc url (JDBC_DATABASE_URL), not postgres (the DATABASE URL) to translate the database URL into the jdbc URL. Note that the first line of postgres says the next line, which starts with jdbc postgresql ql , is added to the word postgres .

 postgres://<username>:<password>@<host>:<port>/<dbname> 

The above format is assigned to the postgres hero. but the game expects below format.

 jdbc:postgresql://<host>:<port>/<dbname>?user=<username>&password=<password> 

Note. In the above url don't forget to add ql to the end of jdbc:postgres + ql becomes jdbc:postgresql

Also add the line below to play back conf

 slick.dbs.default.db.connectionTestQuery="SELECT 1" 

Finally, your application.conf configuration file becomes

 slick.dbs.default.driver="slick.driver.PostgresDriver$" slick.dbs.default.db.driver="org.postgresql.Driver" slick.dbs.default.db.url="jdbc:postgresql://rycmvicwkkzofh: [e-mail] s.com:5432/d5pr4h65obtb0s?user=rycmuicwkkzofh&password=copiedfromheroku" slick.dbs.default.db.user=rycmuicwkkzofh slick.dbs.default.db.password="copiedfromheroku" slick.dbs.default.db.connectionTestQuery="SELECT 1" 

Answer 4

I had the same problem, and after upgrading to HikariCP-2.4.0 and Postgresql-9.4, the problem was resolved :)

Answer 5

Using

 slick.dbs.default.driver="slick.driver.PostgresDriver$" slick.dbs.default.db.dataSourceClass = "slick.jdbc.DatabaseUrlDataSource" slick.dbs.default.db.driver="org.postgresql.Driver" slick.dbs.default.db.url=${JDBC_DATABASE_URL}