You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Stephen Charles Huey <st...@fastmail.fm> on 2004/09/01 01:12:19 UTC
website going down
We had a problem where our website would hang because Tomcat couldn't
access the main database over DSN (on another machine), and it was a
problem with our vendor's ODBC driver, so we moved to the Linux version
(which was more stable). We had created a Watchdog program that would
call a JSP with simple database access, and it would restart Tomcat
whenever the problem occurred (although that sometimes wasn't
sufficient--sometimes we would also have to go in and manually restart
the ODBC driver). Anyway, our problems have lightened considerably, and
consequently our watchdog program doesn't have to do much, although from
once in a while it does restart Tomcat for us.
However, we are now seeing a new problem. The watchdog program will
keep going along as if there's no problem, and yet the website will be
hanging! Because there was a problem in the early days of development
with using the main database for the basic authentication used to enter
our website, we set up a MySQL database on the same machine as Tomcat
and have it access that small database locally by telling it to use
JDBCRealm in our server.xml file. The watchdog program doesn't access a
secure JSP, so it doesn't really have to log in.
In other words, as far as I can see, Tomcat must be trying to go to
MySQL to pop up that basic authentication box, but the box never pops up
because I suppose MySQL is hanging for some reason. Generally all we
have to do is restart Tomcat to get everything back to normal. My
question is, do you know of any reason why MySQL would be doing this?
Thanks,
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: website going down
Posted by Michael McQuade <m....@sympatico.ca>.
Could the person having problems with Tomcat and MySql contact me at
m.mcquade@sympatico.ca .... I also am having Tomcat/MySql/JDBC problems,
maybe we can talk some.....
Thank You....
Mike
----- Original Message -----
From: "QM" <qm...@brandxdev.net>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Tuesday, August 31, 2004 7:47 PM
Subject: Re: website going down
> On Tue, Aug 31, 2004 at 06:12:19PM -0500, Stephen Charles Huey wrote:
> : In other words, as far as I can see, Tomcat must be trying to go to
> : MySQL to pop up that basic authentication box, but the box never pops up
> : because I suppose MySQL is hanging for some reason. Generally all we
> : have to do is restart Tomcat to get everything back to normal. My
> : question is, do you know of any reason why MySQL would be doing this?
>
> Timeout problems, perhaps? Search the archives: this topic comes up
> frequently, especially with MySQL. There are params you can put in the
> JDBC connection to specify a regular keepalive signal, a DB-level ping
> to be sent from the app.
>
> Barring that, you could write one yourself: mix threads with TimerTask
> and a simple call via your DAOs or whatever.
>
> -QM
>
> --
>
> software -- http://www.brandxdev.net
> tech news -- http://www.RoarNetworX.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: website going down
Posted by QM <qm...@brandxdev.net>.
On Tue, Aug 31, 2004 at 06:12:19PM -0500, Stephen Charles Huey wrote:
: In other words, as far as I can see, Tomcat must be trying to go to
: MySQL to pop up that basic authentication box, but the box never pops up
: because I suppose MySQL is hanging for some reason. Generally all we
: have to do is restart Tomcat to get everything back to normal. My
: question is, do you know of any reason why MySQL would be doing this?
Timeout problems, perhaps? Search the archives: this topic comes up
frequently, especially with MySQL. There are params you can put in the
JDBC connection to specify a regular keepalive signal, a DB-level ping
to be sent from the app.
Barring that, you could write one yourself: mix threads with TimerTask
and a simple call via your DAOs or whatever.
-QM
--
software -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org