java.io.IOException: Async IO operation failed (3), reason: RC: 107 Transport endpoint is not connected
Hi,
Does any one know the reason for below exception and how to fix it?
java.io.IOException: Async IO operation failed (3), reason: RC: 107 Transport endpoint is not connected
at com.ibm.io.async.AsyncLibrary$IOExceptionCache.<init>(AsyncLibrary.java:924)
at com.ibm.io.async.AsyncLibrary$IOExceptionCache.get(AsyncLibrary.java:937)
at com.ibm.io.async.AsyncLibrary.getIOException(AsyncLibrary.java:951)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:705)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1881)
""
"
Thank you in advance.
Regards,
Jayami
***Moderator Edit: Vidyaranjan| Updated Categories***
Accepted Solution
EvonSys (Pvt) Ltd
SG
Hi All,
Found this article in PDN.
Resolution :
This issue is resolved by making the following change to the PRPC operating environment: Increased the WebSphere parameters ConnectionIOTimeOut and ConnectionKeepAliveTimeout.
https://community.pega.com/support/support-articles/sockettime-out-and-io-exception-pega-logiles
Kind Regards,
Jayami Dayarathna
PEG
IN
When are you getting this exception? Invoking SOAP/Rest service? Please specify PRPC version also.
From the stack trace it looks like provided end point url is not configured correctly. It's better to re-check and run the scenario.
EvonSys (Pvt) Ltd
SG
Hi Gangababu,
Thank you for your response.
We are getting this exception in Production enviroment. Version - 7.1.8. We are unable to find the scenario.
Only above details in the log file.
Regards,
Jayami
EvonSys (Pvt) Ltd
SG
Hi,
I found an articale which mentoned the same issue, occured in DEV Portal. Seems this is an browser issue.
SA-514
Regards,
Jayami
PEG
IN
As you are in 7.1.8, this article is for 7.1.5, if you believe browser is the root cause of the issue, you can try replicating the issue in dev with the same version of IE or else observe the pattern for the issue occurrance.
Accepted Solution
EvonSys (Pvt) Ltd
SG
Hi All,
Found this article in PDN.
Resolution :
This issue is resolved by making the following change to the PRPC operating environment: Increased the WebSphere parameters ConnectionIOTimeOut and ConnectionKeepAliveTimeout.
https://community.pega.com/support/support-articles/sockettime-out-and-io-exception-pega-logiles
Kind Regards,
Jayami Dayarathna