2

The Bugzilla import script keeps hitting timeout errors and stopping. They either dump the info below, or else a report of a 500 status from the web server. This is making the import a pain because every ten minutes or so I have to babysit the importer and start it again from the last bug that it failed on.

Error:  The request timed out
Stack Trace:    Hide Stack Trace
System.Net.WebException: The request timed out
  at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) [0x00000] 
  at System.Net.HttpWebRequest.GetResponse () [0x00000] 
  at Wasabi.Runtime.Xml.ServerXmlHttp.Send (System.String postData) [0x00000] 

I have already edited the MySQL configuration to increase the database connection timeout; but from the stack here this looks like it's related to HTTP fetching (from Bugzilla?) Is there a setting I can change to increase this timeout?

The importer doesn't show up in the stack trace, but I assume the lines that lead to that Send call are:

Dim xmlHTTP = New ServerXmlHttp
xmlHTTP.Open "GET", sURL, False
xmlHTTP.Send

The server's on Linux (CentOS), btw.

flag

1 Answer

1

Figured it out. There are two timeouts to adjust in the importBugzilla script.

First, change the SetScriptTimeout call on line 20, so the web server doesn't kill the script:

SetScriptTimeout 99999

Then add a timeout to the XMLHTTPRequest that fetches bug data from Bugzilla -- this can take a long time if there's a gigantic attachment. Add the SetTimeout line right after the New ServerXmlHttp, circa line 106:

Dim xmlHTTP = New ServerXmlHttp
xmlHTTP.SetTimeout 240000 ' 4 minute timeout (for those huge attachment downloads)
xmlHTTP.Open "GET", sURL, False
link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.