cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 9538] New: - CachingOutputStream doesn't handle severed connections
Date Fri, 31 May 2002 14:12:42 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9538>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9538

CachingOutputStream doesn't handle severed connections

           Summary: CachingOutputStream doesn't handle severed connections
           Product: Cocoon 2
           Version: 2.0.2
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: core
        AssignedTo: cocoon-dev@xml.apache.org
        ReportedBy: stuart.roebuck@adolos.co.uk


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.

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message