Question

I’m calling web service (my web service) like this:

var request = WebRequest.Create(Options.ServerUri + Options.AccountId + "/integration/trip") as HttpWebRequest;
request.Timeout = 20000; // 20 seconds should be plenty, no need for 100 seconds
request.ContentType = "application/json";
request.Headers.Add(HttpRequestHeader.Authorization, "Basic " + Convert.ToBase64String(Encoding.UTF8.GetBytes(Options.LoginName + ":" + Options.Password)));
request.Method = "POST";

var serializedData = (new JavaScriptSerializer()).Serialize(trip);

var bytes = Encoding.UTF8.GetBytes(serializedData);

request.ContentLength = bytes.Length;
var os = request.GetRequestStream();
os.Write(bytes, 0, bytes.Length);
os.Close();

request.GetResponse();

LoggingAndNotifications.LogAndNotify(string.Format("Success uploading trip: {0}", trip.TripId), false);

return true;

This code called repeatedly to post new objects. After about 3 calls I start getting timeouts on reguest.GetReponse()

There is no errors on server side, nothing in Event Log. It feels like “something” stops me from repeatedly hitting service. What should I look for? Is it possible with company firewall? Or something wrong with my code?

Answer 1

You should close the response as per the example in the doco.

WebRequest myRequest = WebRequest.Create("http://www.contoso.com");

// Return the response. 
WebResponse myResponse = myRequest.GetResponse();

// Code to use the WebResponse goes here.

// Close the response to free resources.
myResponse.Close();

Hmm. The doco also says

Any public static (Shared in Visual Basic) members of this type are
thread safe. Any instance members are not guaranteed to be thread
safe.

You should probably ask for a lock of some kind.