Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 58604 invoked from network); 2 Jun 2003 14:52:02 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 2 Jun 2003 14:52:01 -0000 Received: (qmail 22343 invoked by uid 97); 2 Jun 2003 14:54:15 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org Received: (qmail 22336 invoked from network); 2 Jun 2003 14:54:14 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 2 Jun 2003 14:54:14 -0000 Received: (qmail 52260 invoked by uid 500); 2 Jun 2003 14:50:11 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 52186 invoked from network); 2 Jun 2003 14:50:10 -0000 Received: from marnier.ucs.louisiana.edu (130.70.132.233) by daedalus.apache.org with SMTP; 2 Jun 2003 14:50:10 -0000 Received: from louisiana.edu (gmh2441@poivre.ucs.louisiana.edu [130.70.132.204]) by marnier.ucs.louisiana.edu (8.11.3/8.11.3/ull-ucs-mx-host_1.6) with ESMTP id h52EoCg17432 for ; Mon, 2 Jun 2003 09:50:12 -0500 (CDT) Sender: gmh2441@louisiana.edu Message-ID: <3EDB6423.D922E441@louisiana.edu> Date: Mon, 02 Jun 2003 09:50:11 -0500 From: Geralyn M Hollerman Reply-To: Tomcat Users List Organization: University of Louisiana at Lafayette X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Tomcat problems every morning. References: <3EDA3863.9030905@ranas.us> <20030601222756.M18261@louisiana.edu> <3EDAA4DD.3000507@ranas.us> <20030602020112.M34808@louisiana.edu> <3EDB50D4.3070600@cymulacrum.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Chong Yu Meng wrote: > You could write a small program (not a servlet) that polls the database > (i.e. connect to the database, retrieve some data, disconnect) at > regular intervals and records to a file both successes and failures. > Then maybe trigger a server reboot when it detects a connection problem. > This will add some overhead to both your app server and database server, > so, be advised. You could run this for a couple of days, just enough to > collect data to show to the DBA's. For the stuff I'm working with, *I'm* the DBA. I thought about trying just what you suggested, but what stopped me was when we had a 4.0.x version of Tomcat running on another server and it didn't display any of the "Communication Link Failure" problems I saw; this all cropped up when I first got my hands on a copy of 4.1.12. I noticed that 4.1.12 was the first version I had where Tomcat did the connection pooling as well, although I didn't *think* I was using it - maybe I'd best take a closer look at that part of the docs! -- Lynn Hollerman. --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org