Re: [h2] JdbcConnectionPool & Auto_Server argument

2016-02-18 Thread Thomas Mueller
Hi, > I mean was PageStore made the default again? No. I can't reproduce this, sorry. Regards, Thomas On Tuesday, February 16, 2016, Adam Law wrote: > Really sorry. I never got the notification of a reply in my email, and > thought everyone was busy. It was an error in the version I was usi

Re: [h2] JdbcConnectionPool & Auto_Server argument

2016-02-16 Thread Adam Law
Really sorry. I never got the notification of a reply in my email, and thought everyone was busy. It was an error in the version I was using 1.4.186. Using 1.4.191, the problem is gone. While on the topic of "errors" in 1.4.186 that aren't in 1.4.191 but didn't seem listed on the changelog, in

Re: [h2] JdbcConnectionPool & Auto_Server argument

2016-01-12 Thread Thomas Mueller
Hi, What is your database URL, which version of H2 do you use, and could you post the exception messages and stack trace please. Regards, Thomas On Friday, January 8, 2016, Adam Law wrote: > Hi, > > I use a connection pool to manage connections. The JdbcDataSource' url > contains the argument

[h2] JdbcConnectionPool & Auto_Server argument

2016-01-07 Thread Adam Law
Hi, I use a connection pool to manage connections. The JdbcDataSource' url contains the argument "AUTO_SERVER=TRUE". Everything works well within my application. But when I use another client (SQL Workbench/J) to connect to the database, it throws the error stating the database is inaccessible