Audium Knowledge Base

Search the Knowledgebase	Jump to ID	Browse by Category
[Advanced Search]

The logs show an error.badfetch error

Article ID:	118
Last updated:	July 10, 2007

Would you like to...

Print this page

Post a comment

User Opinions

100%

(1 vote)

How would you rate this answer?

Helpful

Not helpful

SUMMARY

This article lists some possible causes of this error, and several approaches to address it.

SYMPTOMS

An Audium application's logs indicate that an "error.badfetch" has occured during its execution, with a message similar to the following:

A VoiceXML exception occurred: error.badfetch

RESOLUTION

A bad fetch is an indication of a request on the browser that timed out or that received an error code from the application server when requesting the page. Look at the voice browser logs to see if it received a 404 error, or if there was a timeout trying to reach some resource.

A 404 error might be indicative of a malformed URL, a load balancer mistakenly sending a request to the wrong server (or a server that is not running Audium Call Services), and may also be caused by some packets being left out of the URL.

If it is a time out, that would be an indication that some event that is occurring on the system is causing the response to take so long as to time out. If the activity logs indicate that the error.badfetch is occuring 30 seconds or more after an element is entered, this could be an indication of the element taking a long time to enter. If you believe that this may be the problem, check to see what the fetch timeout on the voice browser is set to. If it is approximately the same time as was taken within the element before the error was logged, then this may be the problem. You can also look at the voice browser logs for more information about what the source of the error is.

If it is indeed timing out during the request, this problem is most often caused by custom code that takes a long time to execute (or that is stuck in a loop, etc.). Either modify the custom code to complete before the voice browser times out, or increase the time that the voice browser waits before giving up and throwing error.badfetch.

Visitor Comments

Comment #1 (Posted by AudiumVance)
The most common cause of an error.badfetch error is that the URI of a static audio file (e.g. WAV, VOX, etc.) cannot be reached. Please review your voice browser's logs to determine the URI that encountered this problem. Quite often, this can be resolved by fixing a typo in the URI field of an audio item in your application, or by ensuring that the server hosting these audio files is accessible by the voice browser.
Comment #2 (Posted by Vijay)
Hi, Even though I agree with your explanation, we have a problem where in the Hotevents are defined for 'error', 'error.badfetch', 'error.badfetch.http' Audium still abruptly disconnects the call. I wonder why the error was not handled by the Audium thrown by the voice browser.
Comment #3 (Posted by Vance)
Great question Vijay. Badfetch errors can occur for many reasons, and in the case you're describing it sounds like they may be resulting from a failure to retrieve VoiceXML. This may be due to a delay on the Audium Call Services side (for example, a custom element taking too long). If the badfetch were instead from a failed media file load, the call would most likely be able to continue as long your Hotevent caught the error.badfetch VoiceXML event. However, when the badfetch is due to a VoiceXML retrieval error, the voice browser is unable to contact Audium Call Services in a timely fashion, and so the call is ended. Your voice browser log should have details about exactly which resource it couldn't fetch. Hope that helps.