cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerardo Lastra (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-5821) CachedOutputStream#maybeDeleteTempFile spawns duplicate response handling, which in turn fails with empty content
Date Wed, 25 Jun 2014 09:46:26 GMT

     [ https://issues.apache.org/jira/browse/CXF-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gerardo Lastra resolved CXF-5821.
---------------------------------

    Resolution: Not a Problem

Never mind, this issue is not caused by CXF itself but by a non-CXF interceptor (an outgoing
one, actually, that wraps the content of the output message on a CacheAndWriteOutputStream,
which then closes the old content, causing the whole re-parsing of the response).

> CachedOutputStream#maybeDeleteTempFile spawns duplicate response handling, which in turn
fails with empty content
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-5821
>                 URL: https://issues.apache.org/jira/browse/CXF-5821
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.7.11
>         Environment: Windows 7, Tomcat 7, JRE 6
>            Reporter: Gerardo Lastra
>
> When performing certain SOAP requests, I was getting an "unexpected EOF in prolog" exception
on parsing the results. After a bit of debugging and adding interceptors it seemed the message
was parsed twice. The first time it had the expected content, but the second time its content
was empty (headers were there though).
> I did a live debug session then, and saw the "duplicate parsing" was coming from the
postClose() being called in maybeDeleteTempFile() at CachedOutputStream.java. Apparently this
only happens when the request is written to a temp file (does this depend on request size?),
as otherwise it won't go into the if block.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message