Return-Path: Delivered-To: apmail-hc-dev-archive@www.apache.org Received: (qmail 64636 invoked from network); 19 Mar 2009 03:34:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Mar 2009 03:34:13 -0000 Received: (qmail 32736 invoked by uid 500); 19 Mar 2009 03:34:13 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 32698 invoked by uid 500); 19 Mar 2009 03:34:13 -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 32681 invoked by uid 99); 19 Mar 2009 03:34:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Mar 2009 20:34:13 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Mar 2009 03:34:11 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 76307234C003 for ; Wed, 18 Mar 2009 20:33:50 -0700 (PDT) Message-ID: <654584868.1237433630468.JavaMail.jira@brutus> Date: Wed, 18 Mar 2009 20:33:50 -0700 (PDT) From: "Asankha C. Perera (JIRA)" To: dev@hc.apache.org Subject: [jira] Commented: (HTTPCORE-193) A Connection close could cause an SSLIOSession to be incorrectly considered as closed in some environments In-Reply-To: <1281490456.1237343870445.JavaMail.jira@brutus> 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 [ https://issues.apache.org/jira/browse/HTTPCORE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683292#action_12683292 ] Asankha C. Perera commented on HTTPCORE-193: -------------------------------------------- Hi Oleg This patch works fine for me on Hudson and for the user on the real environment. Will check it in. Many thanks asankha > A Connection close could cause an SSLIOSession to be incorrectly considered as closed in some environments > ---------------------------------------------------------------------------------------------------------- > > Key: HTTPCORE-193 > URL: https://issues.apache.org/jira/browse/HTTPCORE-193 > Project: HttpComponents HttpCore > Issue Type: Bug > Components: HttpCore NIO > Affects Versions: 4.0 > Environment: This has been seen by an Apache Synapse user, as well as by me on the Hudon build machine > SunOS hudson.zones.apache.org 5.10 Generic_137112-02 i86pc i386 i86pc > This is not seen on my Linux box, Linux asankha 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 > x86_64 GNU/Linux > Reporter: Asankha C. Perera > Assignee: Asankha C. Perera > Fix For: 4.1 > > Attachments: HTTPCORE-193.patch, HTTPCORE-193.patch, linux.log, solaris.log > > > This could be seen on the SunOS machine Hudson, and also if a breakpoint is placed at the line receiveEncryptedData() in SSLIOSession:isAppInputReady() to delay its execution slightly > It seems like the following lines are the cause of the problem: > int bytesRead = receiveEncryptedData(); > if (bytesRead == -1) { > this.status = CLOSED; > } > The Channel not having any more bytes does not indicate a close, since there still could be unencrypted data. Just removing the lines that mark the session as closed seems to fix the issue - but should be reviewed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org For additional commands, e-mail: dev-help@hc.apache.org