harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Ellison (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HARMONY-6259) [classlib][luni] PipedInputStream.read throw different info when IOException is raised
Date Mon, 13 Jul 2009 15:13:14 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Tim Ellison resolved HARMONY-6259.

    Resolution: Fixed

Thanks Li Jing,

Not sure that it makes a huge difference, since they are messages in an IOException that people
should not be dependent upon.

However, I applied the patch to the LUNI module at repo revision r793606 with a minor modification.
 i think the !isClosed check is redundant since the previous check has established that already.

Please verify this fixes the issue for you.

> [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
>         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.

View raw message