Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <11756313.315241285075112784.JavaMail.jira@thor>
Date: Tue, 21 Sep 2010 09:18:32 -0400 (EDT)
From: "Hudson (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Commented: (HARMONY-6636) [classlib][luni]PipedInputStream
 should not throw exception after the write end close
In-Reply-To: <20757186.1381282811333698.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HARMONY-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912965#action_12912965 ] 

Hudson commented on HARMONY-6636:
---------------------------------

Integrated in Harmony-1.5-head-linux-x86_64 #954 (See [https://hudson.apache.org/hudson/job/Harmony-1.5-head-linux-x86_64/954/])
    Apply patch for HARMONY-6636: [classlib][luni]PipedInputStream should not throw exception after the write end close


> [classlib][luni]PipedInputStream should not throw exception after the write end close
> -------------------------------------------------------------------------------------
>
>                 Key: HARMONY-6636
>                 URL: https://issues.apache.org/jira/browse/HARMONY-6636
>             Project: Harmony
>          Issue Type: Bug
>            Reporter: Li Jing Qin
>            Assignee: Regis Xu
>             Fix For: 5.0M16
>
>         Attachments: HARMONY-6636-v2.diff, HARMONY-6636-v3.diff, HARMONY-6636.diff
>
>
> When write end closed first, read end should not throw exception when read.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.