Did autoreconnect solve your problem?
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
I don't think autoReconnect would help. It'd still throw the exception
and then re-connect to the database so the code can retry.
Unfortunately it doesn't just silently reconnect and perform the query.
You have configured both testOnBorrow and a validation query, so the
connection is verifie
Hi David,
will give that a try. If the exception persists, I'll go for
autoreconnect, will report here.
Cheers
Gregor
--
what's puzzlin' you, is the nature of my game
gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2
gpgp-key available @ http://pgpkeys.pca.dfn.de:11371
: Monday, June 04, 2007 1:17 AM
To: Tomcat Users List; [EMAIL PROTECTED]
Subject: Re: Strange MySQL-Behaviour with JDBC-Realm
Hi David,
from
http://dev.mysql.com/doc/refman/4.1/en/connector-j-reference-configuration-p
roperties.html:
[snipp]=
If the hostname is not specified
Hi David,
from
http://dev.mysql.com/doc/refman/4.1/en/connector-j-reference-configuration-properties.html:
[snipp]=
If the hostname is not specified, it defaults to 127.0.0.1. If the
port is not specified, it defaults to 3306, the default port number
for MySQL servers.
=
Shouldn't your connection URL look something like this:
jdbc:mysql//db:3306/apacheSSO instead of jdbc:mysql://db/apacheSSO? Not
sure if this means anything, since you say it's already working... It just
looks strange.
-Original Message-
From: Gregor Schneider [mailto:[EMAIL PROTECTED]
S
