[
https://issues.apache.org/jira/browse/AXIS2-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148803#comment-17148803
]
Robert Lazarski commented on AXIS2-5487:
----------------------------------------
I don't see anything httpclient4 related in the stacktrace, I suppose that may
be normal. Looks like that message is still in the latest apache commons
httpclient repo.
Anyways, you are running Linux right? Looks like you might be running into some
type of OS limit maybe. When you get this error, what does this show as the
account user that runs the server? The default value of 1024 is too low for
many use cases.
ulimit -n
lsof -u myuser | wc -l
> 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
> Priority: Major
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
