[
https://issues.apache.org/jira/browse/AXIS2-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15116889#comment-15116889
]
Andreas Veithen commented on AXIS2-5487:
----------------------------------------
No, I think that the debug logs suggest that this is just an incorrect usage of
AUTO_RELEASE_CONNECTION (see AXIS2-3478), i.e. a user error. Anyway the OP
never responded to requests for additional information, so there is not much we
can do.
> 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
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
