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 D2ACE10A5E for ; Tue, 2 Jul 2013 20:41:20 +0000 (UTC) Received: (qmail 92894 invoked by uid 500); 2 Jul 2013 20:41:20 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 92850 invoked by uid 500); 2 Jul 2013 20:41:20 -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 92841 invoked by uid 99); 2 Jul 2013 20:41:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jul 2013 20:41:20 +0000 Date: Tue, 2 Jul 2013 20:41:20 +0000 (UTC) From: "Tad Whitenight (JIRA)" To: dev@hc.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HTTPCORE-345) Resource leak in EntityAsyncContentProducer when produceContent is never called MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Tad Whitenight created HTTPCORE-345: --------------------------------------- Summary: Resource leak in EntityAsyncContentProducer when produceContent is never called Key: HTTPCORE-345 URL: https://issues.apache.org/jira/browse/HTTPCORE-345 Project: HttpComponents HttpCore Issue Type: Bug Components: HttpCore, HttpCore NIO Affects Versions: 4.2.4 Environment: Tested on Sun JDK 6 Linux 64 & Win 32 Reporter: Tad Whitenight The HttpAsyncContentProducer javadoc does not mention that the produceContent method must be called. However, the close() method of EntityAsyncContentProducer assumes that the produceContent method was previously called. Quickly cancelled requests made to an HttpAsyncService can realize this scenario and thus leak resources backing response entities. I discovered this issue in 4.2.4, but am currently reproducing the issue with trunk. I'll attach a simplified test case shortly. A possible fix is to check if the channel was never created and close the underlying entity in this case. -- 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