Return-Path: X-Original-To: apmail-tomcat-dev-archive@www.apache.org Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 70B16DD79 for ; Fri, 9 Nov 2012 11:47:49 +0000 (UTC) Received: (qmail 98056 invoked by uid 500); 9 Nov 2012 11:47:48 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 97609 invoked by uid 500); 9 Nov 2012 11:47:44 -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 97431 invoked by uid 99); 9 Nov 2012 11:47:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Nov 2012 11:47:42 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.115] (HELO eir.zones.apache.org) (140.211.11.115) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Nov 2012 11:47:40 +0000 Received: by eir.zones.apache.org (Postfix, from userid 80) id 70478AF7E; Fri, 9 Nov 2012 11:47:19 +0000 (UTC) From: bugzilla@apache.org To: dev@tomcat.apache.org Subject: [Bug 54116] Deadlocks with mysql driver Date: Fri, 09 Nov 2012 11:47:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Tomcat Modules X-Bugzilla-Component: jdbc-pool X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: casado.alfredo@gmail.com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: dev@tomcat.apache.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://issues.apache.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org https://issues.apache.org/bugzilla/show_bug.cgi?id=3D54116 --- Comment #2 from Alfredo Casado --- Thanks for your response. Please can you answer my second question: =C2=BFif the Pool-Cleaner thread = is blocked how this affect the behaviour of the pool?, =C2=BFthe pool is no lo= nger "clean" unused connections?. If this is true the problem is really a big is= sue in production environments using tomcat+mysql. In the first place i go to mysql driver project issue manager, i found one report of a identical bug and following the recomendations in this issue i'm here contacting with "my pool vendor". As you can see now i have two deadlo= cks: one in my production servers and the second one in this bug resolution. As you can see in the mysql bug they insist that the pool implementation mu= st call abort() instead of close(). I'm not sure what are the implications of this. I'm not an expert in JDBC spec and in driver's or pool's implementations details, i can't judge if the problem is in mysql driver like you say or if= the problem is in pool implementations, like the mysql guy say. I have the following options: - go again to mysql issue manager and reopen the bug.=20 - don't use jdbc-pool (i think that others pool implementations call close = in the same way, the option is not using a pool at all) - don't use mysql j/connector driver. =C2=BFis there another mysql driver implementation i can use? =C2=BFwhat do you recomend? --=20 You are receiving this mail because: You are the assignee for the bug.= --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org