BadFetch Error due to TimeOut

[awaneeshp]

Hi,

We are running our application & after successfully working for about 7 minutes. The call become nonresponsive. After looking at the call log, we found out that this is a time out error.

After that we added the fetchtimeout =180s in submit node. But still we are getting the same behavior.

The error is as fllows:

Error fetching document due to Operation timed out with 0 out of -1 bytes received
DocumentParser::FetchBuffer - could not open URL: http://66.109.47.37/Captira.ADI.UI/menupage.aspx
DocumentParser::FetchDocument - exiting with error result 2
errno: 203 uri http://66.109.47.37/Captira.ADI.UI/menupage.aspx
received event: error.badfetch

For debugging our application on every request we are generating a log file & if the call falis due to an application error then an empty file gets generated. But it seems that on getting the above error, we are not even generating an empty file. Which means that the call is not reaching to our application server & the call becomes silent.

Please let us know how to get rid of this situation becuase its pretty inconsistent & it's not working even after increasing the 'fetchtimeout' attribute of the Submit node.

Thanks,
-Awaneesh

[support]

As you can see from the IVR error message, the IVR can't fetch the document because your webserver is not responding (hence the 0 bytes out of -1 bytes: it's received no data from your web server and thus doesn't even know the size of the document). I'd recommend lowering the fetchtimeout to something like 2 to 5 seconds and to play a "we're having technical difficulties" message when your web server does not respond to queries.

Please note that there's no way for your IVR application to trap debugging information if it's not even responding to queries. You'll have to trap IVR errors on the IVR side and look to improving either your network infrastructure or resolving performance issues on your application server.

[awaneeshp]

You are right that the IVR is not fetching any document from application server.

But if at all the control is reaching to our application server then the first line of the code creates a log file (if error then 0 kb file gets created else the session is written in the file) & followed by the VXML creation which is sent later on to the IVR.

But nothing happens even on our application server becuase the control doesn't seem to reach at our application sometimes becuase a 0kb file is even not getting cretaed & hence the failure.

Please let us know what could be the possble resolution to this issue & how should we trap the detailed error messages on IVR side becuase what i m getting is only "badfetch error" as error description & hence no clue from this which causes its failure.

Thanks.
-Awaneesh

[support]

I don't believe, other than trapping the error.badfetch, there's anything else we can help you with here. I'd recommend reviewing your network setup and your web server configuration. If your web server is either slow or performs badly, your IVR app server scripts may never get executed at all.

[awaneeshp]

Hi,

I have tried to recreate the bad fetch error & the scenario is as follows.

If i call the IVR & get the VXML document from our server & keep moving in the same document by touching almost all the nodes or repeating them for about 3 min . And then submit the request to our application server then we get the "error.badfetch".

This means that if we are moving in any current document on IVR for around 3 min or more than that then we get the bad fetch error.

After getting this error, i m trying to terminate the session by calling an error page on my application server being in the badfetch error node which successfully calls our application serevr & terminates the current caller session as well as the application by returning back a VXML with "Exit" node to the IVR for ending the call.

Now the question is that i m successfully able to terminate the application but couldn't able to find the reason behind the bad fetch because i m calling my application again even after receving the badfetch error for terminating the call which successfully gets executed.

Now i would like to know if you have ever heard this kind of situation. Please suggest & help.

Thanks,
-Awaneesh

[support]

You might consider catching the error.badfetch and resubmitting the request. Alternatively, it might be a configuration issue on your web server in how it handles persistent HTTP/1.1 connections rather than an IVR issue. You should consult your web server configuration guide and look into disabling persistent HTTP connections.