Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-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 6B1F89CE4 for ; Wed, 28 Dec 2011 15:12:56 +0000 (UTC) Received: (qmail 1135 invoked by uid 500); 28 Dec 2011 15:12:55 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 977 invoked by uid 500); 28 Dec 2011 15:12:54 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 957 invoked by uid 99); 28 Dec 2011 15:12:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Dec 2011 15:12:54 +0000 X-ASF-Spam-Status: No, hits=-2001.3 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Dec 2011 15:12:52 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 9CE4712D873 for ; Wed, 28 Dec 2011 15:12:30 +0000 (UTC) Date: Wed, 28 Dec 2011 15:12:30 +0000 (UTC) From: "Brett Bergquist (Created) (JIRA)" To: derby-dev@db.apache.org Message-ID: <1383822581.48674.1325085150644.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Created] (DERBY-5560) Java deadlock between LogicalConnection40 and ClientXAConnection40 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Java deadlock between LogicalConnection40 and ClientXAConnection40 ------------------------------------------------------------------ Key: DERBY-5560 URL: https://issues.apache.org/jira/browse/DERBY-5560 Project: Derby Issue Type: Bug Components: Network Client Affects Versions: 10.8.2.2 Environment: Solaris 10 Glassfish V2.1.1 ClientXADataSource connection pool setup to close all connections on any error Reporter: Brett Bergquist There is a Java deadlock between LogicalConnection40 and ClientXAConnection40. The order of calls that cause the deadlock are: Thread 1 ---- LogicalConnection.close ClientPooledConnection.recycleConnection Thread 2 ---- ClientPooledConnection.close LogicalConnection.nullPhysicalConnection Thread 1 acquires a lock on the LogicalConnection and attempts to acquire a lock on the ClientPooledConnection Thread 2 acquires a lock on the ClientPooledConnection and attempts to acquire a lock on the LogicalConnection In production this occurs when one thread is committing a transaction and another thread is trying to close the connection. This occurred because the Glassfish connection pool is setup to close all connections on any error on any connection and an error has been detected on another connection in the pool. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira