Learn F5 Technologies, Get Answers & Share Community Solutions Join DevCentral

Filter by:
  • Solution
  • Technology
Answers

An error occured while fetching the URI

I have an intermittent problem which I suspect is due to web acceleration. The following error is being produced intermittently when navigating through one of our virtual servers.

"An error occured while fetching the URI. Please retry."

Anyone seen this before? Does anyone have a resolution?
0
Rate this Question

Answers to this Question

placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER
Would you provide the specific URI that is causing the error?
0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER
This site is accessible outside of our firewall. But the request is something like http://test.ourdomain.org/books. I contacted F5 support and there response is below. Looks like we might have to adjust our read/write timeout. I'll have to look deeper into to this, I don't want to screw up the other web accel applications.

SOL9367: HTTP 503 Service Unavailable response: An error occurred while fetching the URI. Please retry.
https://support.f5.com/kb/en-us/solutions/public/9000/300/sol9367.html

Here's the content:

" For client requests to a BIG-IP WebAccelerator-enabled virtual server, if the BIG-IP WebAccelerator does not receive a response from the origin web server within the Read/Write Timeout value, the BIG-IP WebAccelerator sends the client an HTTP 503 Service Unavailable response that appears similar to the following example :
An error occured while fetching the URI. Please retry.
The default Read/Write Timeout value is 30 seconds with two retries. "

You will have more information looking at: https://support.f5.com/kb/en-us/products/wa.html via the administrator Guide.
0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER
We have seen the same error for an SAP application with WAM configured. It's a bit confusing with those timeout and retries settings for destination host. We changed "Retries" from 2 to 0, which helped to avoid most of the duplicate requests to the backend system, and then extended both "timeout" and "R/W" to around 120 seconds, to minimized that URI error, maybe should extend timeout value more to totally get rid of the URI error. I'm not sure, waiting for application test feedback.
0