Question

7
Replies
6479
Views
HARIKUMAR_ALAMPURU Member since 2011 39 posts
TATA CONSULTANCY SERVICES
Posted: April 3, 2017
Last activity: May 24, 2017
Closed

Async IO operation failed (3), reason: RC: 107 Transport endpoint is not connected

Hi, We are seeing the below errors in the logfiles.

Problem retrieving input data: [java.io.IOException: Async IO operation failed (3), reason: RC: 107 Transport endpoint is not connected

Could see multiple PDN Articles with references to the above exception.

https://pdn.pega.com/support-articles/sockettime-out-and-io-exception-pega-logiles

https://pdn.pega.com/community/product-support/question/javaioioexception-async-io-operation-failed-3-reason-rc-107

https://pdn.pega.com/support-articles/user-not-able-login-avaya-using-pega-telephony-toolbar

All of them point to same Resolution : This issue is resolved by making the following change to the PRPC operating environment: Increased the WebSphere parameters ConnectionIOTimeOut and ConnectionKeepAliveTimeout.

Even we want to apply the same Fix for our Client Application Environment which is running on Websphere 7.X . But before that I've read IBM HELP Article regarding these settings.

IBM Recommends - to configure this settings only if your Websphere Application Version is Pre 6.0 which means this Setting is not applicable for Websphere 7.X ? or Higher versions above 6.X ?

Please see below

https://www.ibm.com/support/knowledgecenter/SSAW57_7.0.0/com.ibm.websphere.nd.doc/info/ae/ae/xrun_transport.html#Transport_ConnectionIOTimeout

Can anyone review this & advise further on how to proceed ?

System Administration
Moderation Team has archived post
Share this page LinkedIn