HTTP[8] error

[russell]

Hi,

When I use the services menu or when the idle messages cycle through the phone, occasionally there is this "HTTP[8] error!" thrown on the phone. I don't find anything at my end (web server logs) so I have no idea how to get this fixed. I have seen in 3.3.3/4.0.1 CCM and with 7940/7940.

Has anyone seen this and has a resolution?

Thanks in advance.

[aaronw.ca]

Error 8 is a generic error ("Unknown HTTP Error") which could be caused by a number of issues.

I would suggest checking the URLs of the services being called to ensure that they work (try them from a browser). You might also want to ensure that the phone has the correct DNS settings so that it can resolve any non-IP hostnames.

You may have a problem with one of the URLs that is cycled through in your idle url app. Check the URLs in your idle app loop and ensure that they are all correct.. one (or more) of them may be incorrect.

Note that you can see a phone's services list from a web browser by typing in an URL like:

http://callmanagerserver/CCMCIP/getservicesmenu.asp?name=SEP...

where SEP... is the phone's device name. This can give you a list of URLs to try from another browser.

[russell]

The URL works fine from a browser. Infact, it works even from the phone except for these sporadic occasions. I have tried with and without DNS with IP/host names accordingly but no particular pattern.

The same with the idle URL. They work most of the times but sometimes throw this Error 8. I have always suspected this to be some sort of timeout issue. What do you think? Any other resolutions you can think of?

[aaronw.ca]

Could be a sporadic error with the refresh tag, though hard to say. Is the web server slow to respond sometimes?

Do the logfiles on the web server indicate anything, or any hint of trouble with serving a page around the time of the message? That's the first thing that comes to mind, though you noted that you checked that already.

I assume that you have an idle url that cycles through a variety of URLs to display various messages. Do you know the order of those URLs, and can you track that on the web server to see if there is any consistancy in which URL leads to the problem? How many URLs does a phone typically cycle through before getting the error? Is there any consistancy to the error, or is it random?

My best guess would be that at some point the service refreshed to an invalid URL which the phone could not resolve, at which point it throws the "error 8" message.

I suppose the phone could be "busy" during one of the refresh cycles, though considering the fact that it is not doing much at the time (which is why the idle url is being displayed) I can't see a reason for that.

Just to throw out a random thought, you could put an expiration tag (ie Response.Expires = -1; ) on the idle url (something to do with the history stack?). Just a shot in the dark.

[russell]

The web server is slow to respond sometimes. That is the reason I am leaning towards some kind of timeout issue here. The log files don't indicate any trouble but i can tell the response is slow on a few occasions. I guess I have see if these things happen at the same time.

There is no consistency in the URL where this fails. I have put an expiration tag but it doesn't help.

Thanks for the suggestion. Let me see if the response time is tied to this. I will surely let you know.

Thanks

-R