Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Date: Tue, 31 Aug 2004 18:47:41 -0500
From: QM <qm300@brandxdev.net>
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: Re: website going down
Message-ID: <20040831234740.GA21843@strange.dreamhost.com>
References: <1093993939.9618.203444358@webmail.messagingengine.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1093993939.9618.203444358@webmail.messagingengine.com>
User-Agent: Mutt/1.3.28i

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