Return-Path: X-Original-To: apmail-hc-dev-archive@www.apache.org Delivered-To: apmail-hc-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 A496FD3D0 for ; Mon, 28 Jan 2013 23:17:14 +0000 (UTC) Received: (qmail 89844 invoked by uid 500); 28 Jan 2013 23:17:14 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 89794 invoked by uid 500); 28 Jan 2013 23:17:14 -0000 Mailing-List: contact dev-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list dev@hc.apache.org Received: (qmail 89674 invoked by uid 99); 28 Jan 2013 23:17:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2013 23:17:14 +0000 Date: Mon, 28 Jan 2013 23:17:14 +0000 (UTC) From: "Scott Stanton (JIRA)" To: dev@hc.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HTTPCORE-331) deadlock in AbstractNIOConnPool MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HTTPCORE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564826#comment-13564826 ] Scott Stanton commented on HTTPCORE-331: ---------------------------------------- I applied the patch and so far the problem has not recurred. I think you can close this as fixed now. > deadlock in AbstractNIOConnPool > ------------------------------- > > Key: HTTPCORE-331 > URL: https://issues.apache.org/jira/browse/HTTPCORE-331 > Project: HttpComponents HttpCore > Issue Type: Bug > Components: HttpCore NIO > Affects Versions: 4.2.3 > Environment: jjdk 1.7.0_u10 > Reporter: Scott Stanton > Priority: Critical > Fix For: 4.2.4, 4.3-alpha2 > > Attachments: stacks > > > I have run into a deadlock in the AbstractNIOConnPool. I have attached the deadlock stacks. I'm not entirely sure what's going on yet, but it appears that nested futures are causing lock ordering problems. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org For additional commands, e-mail: dev-help@hc.apache.org