Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 36518 invoked from network); 15 May 2007 14:48:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 May 2007 14:48:31 -0000 Received: (qmail 19400 invoked by uid 500); 15 May 2007 14:48:32 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 19348 invoked by uid 500); 15 May 2007 14:48:32 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 19335 invoked by uid 99); 15 May 2007 14:48:32 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 May 2007 07:48:32 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [212.27.42.65] (HELO smtp8-g19.free.fr) (212.27.42.65) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 May 2007 07:48:24 -0700 Received: from [192.168.0.11] (lan31-8-82-247-178-12.fbx.proxad.net [82.247.178.12]) by smtp8-g19.free.fr (Postfix) with ESMTP id C99C719D5A for ; Tue, 15 May 2007 16:48:03 +0200 (CEST) Message-ID: <4649C821.1040907@apache.org> Date: Tue, 15 May 2007 16:48:01 +0200 From: Remy Maucherat User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: [VOTE] Release build 6.0.13 References: <4640A567.3060400@apache.org> <7a0107ba0705150634t466a7772y6b29edf21e513bfd@mail.gmail.com> In-Reply-To: <7a0107ba0705150634t466a7772y6b29edf21e513bfd@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Martin Dubuc wrote: > I have been using 6.0.13 for a few days. I was using 6.0.11 for some > time up to then. My app was running pretty smooth with 6.0.11. I do > not not if it is a coincidence or not, but since seitching to 6.0.13, > I have seen a few cases of Java exceptions, all seems to be related to > MySQL Connector/J connection timing out. I am wondering if anything > has changed in Tomcat since version 6.0.11 that could explain this > kind of issue. DBCP was updated in 6.0.11, but has not been changed since that build. R�my --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org