brachid
asked on
java.io.IOException: Async IO operation failed, reason: RC: 32 Broken pipe
Hello,
We've got 2 applications calling Client and Server running on the same instance server on WAS6.1, recently with an update of the application, CPU reaches 95% to 98%, checking the logs I've got many of "java.io.IOException: Async IO operation failed, reason: RC: 32 Broken pipe".
Client application is an X-Fire application calling Webservices on Server application running both of them on the same instance.
Making some research I found that this error could happen if "HttpInboundPersistReadTim eout" is exceeded.
Is there any tunning to do except raising up the value of this propertie.
Developpers said that the function didn't change with the application update and it consist of running an Oracle Package to send answers to the cleint side.
Any help please.
Rachid,
error-log
We've got 2 applications calling Client and Server running on the same instance server on WAS6.1, recently with an update of the application, CPU reaches 95% to 98%, checking the logs I've got many of "java.io.IOException: Async IO operation failed, reason: RC: 32 Broken pipe".
Client application is an X-Fire application calling Webservices on Server application running both of them on the same instance.
Making some research I found that this error could happen if "HttpInboundPersistReadTim
Is there any tunning to do except raising up the value of this propertie.
Developpers said that the function didn't change with the application update and it consist of running an Oracle Package to send answers to the cleint side.
Any help please.
Rachid,
error-log
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
This issue cant be resolved by a code as it is not related to the program and external to the JVM. Please check how frequent are you getting this. Any specific pattern/action when it occurs. Once identified, please consult with network person.
By the way, if both the applications are on the same instance, then how communication is happened. I mean using IP address (or localhost) ? If IP address is specified then network comes into the picture. Please give it a try by using localhost.