Question
TATA CONSULTANCY SERVICES
US
Last activity: 24 May 2017 11:14 EDT
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/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.
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/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
Can anyone review this & advise further on how to proceed ?
Swedbank AB
SE
Hello,
After reviewing the first link, I came to know that the user was on WAS 7.X.
Thus, I believe you should go ahead and make the necessary changes.
Sincerely,
Pawan
TATA CONSULTANCY SERVICES
US
HI Pawan,
Thanks for replying to this Post. But the IBM HELP Article says - to avoid using these parameters, as these parameters are applicable only for PRE WAS Versions 6.X .
Per IBM Article : If the users are using a higher WAS Versions - it is recommended to use HTTP Transport Channel Custom Properties.
So, due to this I'm bit confused on the fix that was suggested in the PDN Support Article.
https://community.pega.com/support/support-articles/sockettime-out-and-io-exception-pega-logiles
Do we know for the Client (application which is on WAS 7.X) who applied the Fix as per PDN Suggested article - did it resolved the issue ? Did we get any confirmation from that User/Client ?
Thanks
HARI KUMAR ALAMPURU
TATA CONSULTANCY SERVICES
US
Can anyone help me on this.
Support Articke ID -- SA ID: SA-3174
Thanks
Hari Kumar Alampuru
Pegasystems Inc.
DE
This is primarily an issue of WebSphere administration and only loosely related to PRPC at all.
But as said in the IBM Help article that you quoted: "Refer to HTTP transport channel custom property for a description of how to specify this property for an HTTP transport channel."
This description can be found here (for WAS 7.x): https://www.ibm.com/support/knowledgecenter/SSAW57_7.0.0/com.ibm.websphere.nd.doc/info/ae/ae/urun_chain_typehttp.html
There you can read: "[...]The value specified for this property, in conjunction with the value specified for the Write timeout property, provides the timeout functionality that the ConnectionIOTimeout custom property provided in previous releases."
So in regard of your reported problem, basically only the name for the parameter has changed. For further details, please contact your IBM WebSphere Support.
TATA CONSULTANCY SERVICES
US
Thank you. Will try to implement this fix.
American Express
US
HI Team,
can you please suggest what is the fix for this issue - we are also facing the same issue
Problem retrieving input data: ;java.io.IOException: Async IO operation failed (1), reason: RC: 107 Transport endpoint is not connected
Regards,
Manoj