search

lbehnke / h2database

Automatically exported from code.google.com/p/h2database
0 stars 0 forks source link

"Login timeout" with embedded DB #77

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
java.sql.SQLException: Login timeout
    at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:204)

Database is a 1.5G embedded database with cached tables
h2-1.1.111.jar

(Sorry, the strack-trace is not longer and no other information concerning
this issue is logged)

Original issue reported on code.google.com by Marcus.W...@gmail.com on 20 Apr 2009 at 5:01

GoogleCodeExporter commented 9 years ago 
There seems to be a bug in the startup code so that indexes of some big 
database are
re-built every time the database is opened.

Still, I probably need to change the default login timeout to 15 minutes. That 
should
be enough in the worst case.

Original comment by thomas.t...@gmail.com on 20 Apr 2009 at 5:08

GoogleCodeExporter commented 9 years ago 
That is consistent with what I've seen.
Startup takes longer if the database is bigger.

However the LoginTimeout happens after the database has already been reat a few 
times.
I counted 11 open connections at the time it happens. I can reproduce
it easily if there is anything you want me to look at.

Original comment by Marcus.W...@gmail.com on 20 Apr 2009 at 5:30

GoogleCodeExporter commented 9 years ago 
This is a bug in the current version that causes the indexes to be re-created 
again
and again when opening the database. This will be fixed. Also, I will change the
default login timeout to 5 minutes - I hope this is enough.

Original comment by thomas.t...@gmail.com on 27 Apr 2009 at 6:30

GoogleCodeExporter commented 9 years ago 
5min seems pretty high for a timeout.
Is this only in the client-server -case
or also in the case of embedded operation?

In an embedded database I would not expect
a user to wait up to 5 minutes before the
application has started. Especially if more
then one plugin uses an embedded database.

Original comment by Marcus.W...@gmail.com on 28 Apr 2009 at 5:44

GoogleCodeExporter commented 9 years ago 
> 5min seems pretty high for a timeout.

Sure, it's high. However there are situations where it can take long (when 
indexes
need to be re-built).

Original comment by thomas.t...@gmail.com on 30 Apr 2009 at 4:40

GoogleCodeExporter commented 9 years ago 
In the latest version the login timeout is 5 minutes.

Original comment by thomas.t...@gmail.com on 1 May 2009 at 4:00