This content has been marked as final. Show 7 replies
This error is also not persistent. it comes on its will. We can not always reproduce it.
Whenever this error comes. We try after some time again with the same scenario and it passes.
Is it an external web-service that you are invoking?
If it is, then it could be an issue with that service. Maybe it is a load-balancer endpoint and one or more of its nodes are down?
This could explain the intermittent issue.
Yes it is a external WS which is running on another Weblogic server in the same network.
We do have loadbalancer also in between but all nodes are fine.
You get this error when server did not respond your request1 person found this helpful
when the target machine is overloaded with lot of requests
or when the server takes more time to process the request like http timeouts.
These scenarios are quite frequent in webservices flow. You can either retry the request or gracely terminate.
Edited by: helloprasanna on Nov 14, 2012 2:07 PM
yeah, I am doing the same thing.
first retrying and then terminating.
Please let me know if there are some suggestions which can avoid this situation.
How are you handling the retry options, increase the retry count and interval.
If your frequency of retry interval is very minimal there is no point in retry.
Increase the interval time and then try.
It looks like your already handling it right.
But if there are lot of such error messages popping up then you need to identify and fix the issue.
How to do it?
1. Do performance testing on the end service and identify the throughput of your end service.
2. Throttle your proxy services and business services to push the load below the agreed limit.