[
https://issues.apache.org/jira/browse/AXIS2-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811868#comment-13811868
]
Kishanthan Thangarajah commented on AXIS2-5487:
-----------------------------------------------
As per HTTPCLIENT-910, its mentioned that this will not be fixed for HC 3.x
versions. And the recommendation was to upgrade to HC 4.x. Since axis2 trunk
currently has support for HC 4.x, we can resolve this. If anyone else face the
same issue with 1.6.2, they can consider upgrading to 1.7.
> Attempted read on closed stream - II
> ------------------------------------
>
> Key: AXIS2-5487
> URL: https://issues.apache.org/jira/browse/AXIS2-5487
> Project: Axis2
> Issue Type: Bug
> Components: client-api
> Affects Versions: 1.6.2
> Environment: Windows XP SP2, JDK 1.7, AXIS2-1.6.2, Jetty 7.2.0
> Reporter: Espen Rydningen
> Labels: apache-mime4j-core-0.7.2, axiom_1.2.13, axis2_1.6.2
> Fix For: 1.7.0
>
> Attachments: DebugAndStacktrace.txt, wsRequest.txt, wsResponse.txt
>
>
> After upgrading from Axis2 1.5.6 to Axis2 1.6.2 we started receiving this
> "org.apache.axiom.om.OMException: java.io.IOException: Attempted read on
> closed stream."
> WS request and response is attached
> Debug log and stacktrace is attached
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
