getting the exception as*Login
timeout*
and my application is getting stopped...
OK, nice work.
In that case you probably have something locking the whole database for
long periods of time.
Look for very long-running transactions, or for a session that is
opening a transaction and then
On 2012-10-16 11:35, priyanka wrote:
Hello sir,
I have small Question...
My database server is used by 7 clients...because iam connecting remotely
while connecting remotely in h2 database...Iam getting an exception as
login timeout
I have increased lock timeout and mvcc=true... for some
Hello sir,
I have small Question...
My database server is used by 7 clients...because iam connecting remotely
while connecting remotely in h2 database...Iam getting an exception as
login timeout
I have increased lock timeout and mvcc=true... for some time it
works..after that again i get the
ied mvcc=true
Then also iam getting the exception as Login timeout
so my Questions are
1)y? we get login timeout
2)how and where to increase Login timeout or
3)If we connect remotely is there any problem we get login timeout because
remotely only 5 clients we are connecting at once normally connect
Hi,
FYI: There was a bug (the timeout exception was thrown too early), but
that was fixed in version 1.2.141. See also the change log.
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
iddle ground between thread pool size and
> behavior and database connection pool size and behavior.
>
> Joe
>
> On Sep 6, 3:51 pm, Prakash wrote:
>
>
>
> > Thanks Joe,
>
> > Is max connections the same as the size of the pool? I didn't get the
> > Logi
nections the same as the size of the pool? I didn't get the
> Login Timeout error after Increasing the max connections in the
> connection.
> If it is not the same please let me know how to increase the
> connection pool size.
>
> If it is the same, is it advisable to have
Thanks Joe,
Is max connections the same as the size of the pool? I didn't get the
Login Timeout error after Increasing the max connections in the
connection.
If it is not the same please let me know how to increase the
connection pool size.
If it is the same, is it advisable to have value o
gt; connPool.setLoginTimeout(60);
>
> the url also includes the keyworkds, ;AUTO_SERVER=TRUE
>
> Currently I am trying to read records out of the database with say 20
> threads, and am seeing this Login Timeout. I have increased the
> timeout from default 30 seconds to 60 but am s
read records out of the database with say 20
threads, and am seeing this Login Timeout. I have increased the
timeout from default 30 seconds to 60 but am still getting this.
java.sql.SQLException: Login timeout
at
org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.j
Hi,
You are right. The documentation is now updated (30 seconds is the
default), and the wait bug is fixed in the trunk. Thanks for your
help!
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
Hi,
Thanks again for the patch! This problem is now fixed in the trunk. I
also added a test case.
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
Hi,
I agree that cost/benefit don't pay for a more advanced approach on the
getConnection() method only.
This slim and fast built-in connection pool do their job well in their scope.
An industrial strength CP involve many other things and maybe redesign.
I think that's better to maintain this CP
Hi,
Thanks a lot for the patch! It looks good, and I will apply it for the
next release. I hope I can also write a test case. Using
java.util.concurrent is an option, but I don't think it's required
(actually I want to avoid using it for Java 1.4 compatibility). I know
the algorithm is not "fair"
Dario,
The mechanism you describe in your patch is exactly what I was
thinking would do the trick. Specifically it addresses the issue of
properly waiting the configured time interval regardless of how many
cycles it takes.
This approach still has the risk that a waiter could be starved out of
g
ons) {
return getConnectionNow();
}
-if (i >= timeout) {
- throw new SQLException("Login timeout", "08001", 8001);
-}
try {
wait(1000);
ionNow();
}
-if (i >= timeout) {
-throw new SQLException("Login timeout", "08001",
8001);
-}
try {
wait(1000);
} catch (InterruptedEx
t;
> Thank you for the information.
>
>
>> I might just be reading the code wrong or misunderstand the wait/
>> notifyAll behavior...but I'm quite sure I'm seeing these 'Login
>> timeout' exceptions at times way before 30 seconds hit.
>
> I am
isunderstand the wait/
> notifyAll behavior...but I'm quite sure I'm seeing these 'Login
> timeout' exceptions at times way before 30 seconds hit.
I am not in the H2 developer team so I didn't look into the source
code. I think one of the developers should answer th
...but I'm quite sure I'm seeing these 'Login
timeout' exceptions at times way before 30 seconds hit.
Thanks
Joe
On Aug 5, 5:09 am, Wildam Martin wrote:
> On Thu, Aug 5, 2010 at 06:51, Joe wrote:
> > Couple of thoughts:
> > 1) The JDBCConnectionPool setL
On Thu, Aug 5, 2010 at 06:51, Joe wrote:
> Couple of thoughts:
> 1) The JDBCConnectionPool setLoginTimeout method says the default
> timeout is 5 minutes. However, the default is actually set to '30' in
> the code. That appears that is supposed to be '30' seconds.
The default timeout has been r
upts, could be spurious, could be notifyAll)
> and instead track the actual wait time in milliseconds. This way it
> will truly wait that long. This by itself doesn't solve the fairness
> problem but at least you'd know you truly did wait the full login
> timeout period.
>
ness
problem but at least you'd know you truly did wait the full login
timeout period.
Does any of this make sense or am I reading that code incorrectly?
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send
Thanks! You're right. My sync code was wrong.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to h2-database@googlegroups.com
To unsubscribe from this group, send
osed: " + --openConnectionCount);
If the count goes higher than 5 you know there is a problem in your application.
Regards,
Thomas
On Sun, Oct 12, 2008 at 12:32 PM, sproket <[EMAIL PROTECTED]> wrote:
>
> Hi All,
>
> I'm getting the following exception in a web
Hi All,
I'm getting the following exception in a web app I'm writing.
java.sql.SQLException: Login timeout
at
org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:
182)
I think it might be because of the way I'm using the
JdbcConnectionPool.
Because my
26 matches
Mail list logo
