[
https://issues.apache.org/jira/browse/AXIS2-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150772#comment-17150772
]
ANN SONIYA JOHNY commented on AXIS2-5487:
-----------------------------------------
Hi Robert,
Increased the ulimit -n to 4000, but still we see "Attempted read on
closed stream" error
The lsof -u iscpadm was around 1810 only during the entire traffic run.
The below options were disabled for httpclient object.
* HTTPConstants.REUSE_HTTP_CLIENT
* HTTPConstants.AUTO_RELEASE_CONNECTION
Thanks
Ann
> 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
