Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <260033141.1247540774922.JavaMail.jira@brutus>
Date: Mon, 13 Jul 2009 20:06:14 -0700 (PDT)
From: "Li Jing Qin (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Commented: (HARMONY-6259) [classlib][luni]
 PipedInputStream.read throw different info when IOException is raised
In-Reply-To: <1405358304.1246951334796.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Li Jing Qin commented on HARMONY-6259:
--------------------------------------

It does not make a huge difference. But ant (i am investigating on it these
days) treat "Write end dead" differently. It will log the the "Write end
dead" and eat the Exception.
It is absolutely a non-big difference with RI. But it will fail the ant
redirector task.  HARMONY-6260 also in the same situation.


-- 
Yours sincerely,
Charles Lee


> [classlib][luni] PipedInputStream.read throw different info when IOException is raised
> --------------------------------------------------------------------------------------
>
>                 Key: HARMONY-6259
>                 URL: https://issues.apache.org/jira/browse/HARMONY-6259
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>            Reporter: Li Jing Qin
>            Assignee: Tim Ellison
>             Fix For: 5.0M11
>
>         Attachments: HARMONY-6259.diff, HARMONY-6259.v2.diff
>
>
> When the write end is closed unexpectedly, RI returns "Write end dead". Harmony do not differentiate the "Pipe is broken" and "Write end dead"

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