[
https://issues.apache.org/jira/browse/CXF-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588231#comment-13588231
]
Aki Yoshida commented on CXF-4846:
----------------------------------
http://svn.apache.org/viewvc?view=revision&revision=1450509
cxf/branches/2.6.x-fixes/rt/transports/http/src/main/java/org/apache/cxf/transport/http/HTTPConduit.java
> A confusing exception may be thrown from HTTPConduit when oneway call results
> in HTTP 500 response
> --------------------------------------------------------------------------------------------------
>
> Key: CXF-4846
> URL: https://issues.apache.org/jira/browse/CXF-4846
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.6.6
> Reporter: Aki Yoshida
> Assignee: Aki Yoshida
>
> HTTPConduit in 2.6.x does not correctly close the stream for oneway call that
> results in HTTP 500. Instead of closing the error stream, it tries to close
> the input stream. And this leads to a confusing exception message and might
> potentially lead to other issue.
> This problem might be related to the socket already closed exception that has
> been occasionally observed for CXF 2.6.x with recent jdk1.6.0_38 and 39 but
> not with earlier jdk versions.
> Note that this problem is not relevant for 2.7.x and 2.8.x, as HTTPConduit is
> differently implemented in 2.7.x.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
