[ http://issues.apache.org/jira/browse/COCOON-291?page=all ] Helma van der Linden reopened COCOON-291: -----------------------------------------
reopened just to set the resolution to fixed > CachingOutputStream doesn't handle severed connections > ------------------------------------------------------ > > Key: COCOON-291 > URL: http://issues.apache.org/jira/browse/COCOON-291 > Project: Cocoon > Type: Bug > Components: * Cocoon Core > Versions: 2.0.4 > Environment: Operating System: other > Platform: All > Reporter: Stuart Roebuck > Assignee: Cocoon Developers Team > > If a file is being generated by the ResourceReader and an error occurs during > transmission, because the connection is closed before the file is fully > transmitted, then the exception is caught by ResourceReader and the > CachingOutputStream returns the partial output as if it were complete. The > next time the same resource is requested from the StreamCache, only the > partial file is returned. > This fault is present in 2.0.2 and still appears to be present in the new > ProcessingPipeline code. > If the CachingOutputStream could catch "java.io.IOException: Broken pipe" > exceptions and continue to accept write calls until the stream has been > completed (but not passing them to the 'receiver') this would ensure that the > cache contained the complete file, even though the connection has been closed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
