Quote:
Originally Posted by chodsdon
The content server had been working fine for me..but since .16, whenever I test the server or anyone tries to access it, we get a javascript error Error:timeout undefined
Once I clear the error, searches work fine. The page header with the search box loads fine..so it doesn't seem to be a connection issue. It's just that initial timeout error when attempting to load the initial data.
Any ideas? (Still having the problem in .17)
Different browers...Firefox, Opera..no Stanza
|
I can reproduce the problem by making my content server very slow (sticking sleep()s into it).
The message is being printed by jquery.js handleError, line 2843. It is doing what it is supposed to do -- printing a timeout message. The timeout is currently set to be 10 seconds. I put a 15 second sleep into the content server and started seeing the messages.
First question: why is your content server taking more than 10 seconds to respond? Is it on a slow machine? Low memory? Huge library? Any ideas?
Second question: how to fix it. One way is to increase the timeout in gui.js, but that seems like fixing the problem with a hammer. Another way is for you to create a local copy of gui.js and change the value yourself. A third way is to make the timeout into an option (rather complicated, but possible). Kovid, do you have a preference?