cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akitoshi Yoshida (JIRA)" <>
Subject [jira] [Commented] (CXF-6720) AbstractHTTPDestination#WrappedOutputStream.close() calls flush after close
Date Tue, 22 Dec 2015 11:04:46 GMT


Akitoshi Yoshida commented on CXF-6720:

Hi Dan,
thanks for your comments. The current jetty tests are all running fine without the flushBuffer
So I'll remove the line.
regards, aki

> AbstractHTTPDestination#WrappedOutputStream.close() calls flush after close
> ---------------------------------------------------------------------------
>                 Key: CXF-6720
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.7.18, 3.0.7, 3.1.4
>         Environment: IBM Liberty Profile with CXF and JavaMelody, but this is mostly
a discussion about Servlet/Flushable-spec and flush after close.
>            Reporter: John Hestad
>            Priority: Minor
>              Labels: Closable, Flushable, IBM_JAVA, JavaMelody, LibertyProfile, OutputStream,
core, flush, flushBuffer, servlet-api
> Bug location:
> ServletResponse.flushBuffer:
> Reading the javadoc of ServletResponse.flushBuffer, Closable and Flushable interfaces
tells me that calling flushBuffer on a ServletResponse containing a  closed stream could give
an IOException.
> We have had problems with this in Liberty Profile, while using CXF together with CXF.
> Background story:
> 1) Javamelody issue:
> 2) Old discussion:!topic/javamelody/kX31sRTFrHE/discussion
> 3) IBM WasDev issue:
> To make a short recap:
> 1) Soap-call to the service
> 2) Cxf calls close()  -> OutputStream closes
> 3) Cxf calls flushBuffer which hits JavaMelody's ServletResponse-wrapper which again
calls flush on the OutputStream
> 4) Ibm Liberty Profile throws an IOException telling the stream is closed.
> If we exclude JavaMelody:
> 3) Cxf calls flushBuffer which hits Liberty Profile's ServletResponse-wrapper which checks
if the stream is already close and returns early.
> Update: Added crossreference to the IBM WasDev issue from the wrong one:

This message was sent by Atlassian JIRA

View raw message