[
https://issues.apache.org/jira/browse/AXIS2-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525865#comment-14525865
]
Andreas Veithen commented on AXIS2-5487:
----------------------------------------
I think that the theory about HTTPCLIENT-910 is not valid; see my comment on
that issue.
The problem seems the be that the HTTP connection is released too early, i.e.
before the response is read:
{code}
22:09:40 0 0 1 [qtp8669931-13] DEBUG
org.apache.commons.httpclient.HttpConnection releaseConnection - Releasing
connection back to connection manager.
22:09:40 0 0 1 [qtp8669931-13] DEBUG
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager freeConnection
- Freeing connection, hostConfig=HostConfiguration[host=http://localhost:9095]
{code}
You would need to debug your application to determine why this happens (or
provide a test case to reproduce the problem).
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
