cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fedor Malyshkin (JIRA)" <>
Subject [jira] Commented: (CXF-1059) CachedOutputStream closes streams prematurely
Date Mon, 24 Sep 2007 10:44:50 GMT


Fedor Malyshkin commented on CXF-1059:

I experienced almost the same problem when implemented my JAX-WS Provider service and invoked
it with big XML.
It don't close itself, but it is closed by other DataReader's instance.
I didn't keep my exception, but i offer my patch for this problem.

> CachedOutputStream closes streams prematurely
> ---------------------------------------------
>                 Key: CXF-1059
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.1
>         Environment: Windows XP
>            Reporter: Ryan Moquin
>            Assignee: willem Jiang
>         Attachments: CachedOutputStream.patch
> I receive this error when I return a large amount of data from my webservice (and get
past the ClassCastException that I filed a jira about yesterday):
> Sep 22, 2007 7:46:46 PM org.apache.cxf.transport.jbi.JBIDestinationOutputStream commitOutputMessage
> SEVERE: error sending Out message
> Cached file was deleted, C:\DOCUME~1\ryan\LOCALS~1\Temp\att25960tmp
> The system cannot find the file specified)
>         at
>         at org.apache.cxf.transport.jbi.JBIDestinationOutputStream.commitOutputMessage(
> )
>         at org.apache.cxf.transport.jbi.JBIDestinationOutputStream.doClose(
>         at
>         at org.apache.cxf.transport.AbstractConduit.close(
>         at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSender
>         at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
>         at org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(
>         at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
>         at org.apache.cxf.transport.ChainInitiationObserver.onMessage(
>         at org.apache.cxf.transport.jbi.JBIDispatcherUtil.dispatch(
>         at org.apache.servicemix.cxfse.CxfSeEndpoint.process(
>         at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(
>         at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(
>         at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(
>         at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(
>         at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(
>         at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(
>         at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at
> The problem is that the close method in CachedOutputStream closes the stream (and deletes
any temporary file associated) and then indicates the close was made so that child classes
can also perform any closing operations.  The problem is that the JBIDestinationOutputStream
at that point wants to read some data from the stream and hence the above error occurs.  The
methods simply need reordered so that the temp file isn't closed before the doClose is executed.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message