harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Jing Qin (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-6636) [classlib][luni]PipedInputStream should not throw exception after the write end close
Date Tue, 21 Sep 2010 05:55:32 GMT

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

Li Jing Qin updated HARMONY-6636:
---------------------------------

    Attachment: HARMONY-6636-v3.diff

The problem is due to the before read the thread of writer is already dead. It is a time problem.
I have update the test case and also fix the potential bug that pipe still can be read if
write has closed but there were still some thing left in the pipe. 

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


Mime
View raw message