Hi,
OK, the default is now 30 seconds.
Regards,
Thomas
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to h2-datab...@googlegroups.com.
To unsubscribe from this group, send email to
h2-database+unsubscr...@goo
On Tue, May 25, 2010 at 01:09, Kerry Sainsbury wrote:
> ... and I guess if the timeout is configurable, it doesn't matter too much
> what the default is :-)
A good default does matter as mostly defaults are kept - e.g. if your
application does not offer an option for setting the timeout. ;-)
--
... and I guess if the timeout is configurable, it doesn't matter too much
what the default is :-)
On Tue, May 25, 2010 at 10:36 AM, Wildam Martin wrote:
> On Mon, May 24, 2010 at 10:06, Thomas Mueller
> wrote:
> > 15 seconds:
> > http://www.15seconds.com/issue/040830.htm
>
> 15 seconds can be
On Mon, May 24, 2010 at 10:06, Thomas Mueller
wrote:
> 15 seconds:
> http://www.15seconds.com/issue/040830.htm
15 seconds can be reached for slow connection (e.g. mobile internet
connection) and busy server (e.g. backup running) at server side for a
smaller company (with less performant lines and
I'd think that 15 seconds would be fine. If a connection is taking 15
seconds then surely something is seriously wrong? Certainly 5 mins is too
large.
On Mon, May 24, 2010 at 8:06 PM, Thomas Mueller <
thomas.tom.muel...@gmail.com> wrote:
> Hi,
>
> Maybe the default timeout (5 minutes) is too larg
Hi,
Maybe the default timeout (5 minutes) is too large. Maybe a default
timeout between 15 and 180 seconds would make more sense.
15 seconds:
http://www.15seconds.com/issue/040830.htm
180 seconds:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.do
Hi,
so with this timeout setting, it's easy to catch the sqlexception,
create a new connection on the fly, and put a warning in the log at
the same time
Thanks a lot !
Regards,
Romain.
On May 20, 6:51 am, Thomas Mueller
wrote:
> Hi,
>
> It is waiting until a connection is available or the conn
Hi,
It is waiting until a connection is available or the connection
timeout is reached, which is 5 minutes by default. To use a lower
value, for example 5 seconds, use:
pool.setLoginTimeout(5);
See also
http://h2database.com/javadoc/org/h2/jdbcx/JdbcConnectionPool.html#setLoginTimeout_int
Rega
Hi All,
If I instanciate more connection than the max specified by
getMaxConnections(), it seems that getConnection() is waiting forever,
until a connection of the pool is released. Ok, but is there a way to
detect this, and
1/ produce a warning
2/ create despite everything a new connection on the
