You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "jiraposter@reviews.apache.org (JIRA)" <ji...@apache.org> on 2012/05/03 01:03:58 UTC

[jira] [Commented] (OOZIE-828) XLogStreamer has missing i/o stream close statements

    [ https://issues.apache.org/jira/browse/OOZIE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266995#comment-13266995 ] 

jiraposter@reviews.apache.org commented on OOZIE-828:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4975/
-----------------------------------------------------------

Review request for oozie.


Summary
-------

Refer to https://issues.apache.org/jira/browse/OOZIE-828


This addresses bug OOZIE-828.
    https://issues.apache.org/jira/browse/OOZIE-828


Diffs
-----

  trunk/core/src/main/java/org/apache/oozie/util/XLogStreamer.java 1326832 

Diff: https://reviews.apache.org/r/4975/diff


Testing
-------

some end-to-end tests experiencing interruption in getting log stream from multiple gz files
oozie job -log <id>

Testing with patch to see if this is the cause. In either case, these close statements are required.


Thanks,

Mona


                
> XLogStreamer has missing i/o stream close statements
> ----------------------------------------------------
>
>                 Key: OOZIE-828
>                 URL: https://issues.apache.org/jira/browse/OOZIE-828
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: 3.2.0
>            Reporter: Mona Chitnis
>            Assignee: Mona Chitnis
>              Labels: oozie
>             Fix For: 3.2.0
>
>
> XLogStreamer streamLog() function has missing i/o stream close statements at a couple of places. This might hamper accurate i/o of log stream.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira