I'm new to WCF but I've managed to create a working service that's hosted in IIS with GoDaddy. I'm having an odd problem that I didn't experience in development. The service works as it should for about 15 seconds. I can make several calls within this initial 15 second window to the server and receive responses. After 15 seconds, the client's call will timeout at the default 1 min mark with the generic timeout error.
I've traced both the Server and the Client and it seems the Clients request is never reaching the server after this initial 15 seconds. The Client's trace is showing the timeout but it's somewhat generic. The server doesn't show anything, just the last successful call.
I've tried a number of things like adjusting the timeouts, closing/disposing after each call, requesting the WCF service in a BackgroundWorker thread, and a few other things that didn't help. Note I do call the WCF request function from a Timer.
In the Clients trace, there is one odd thing that seems connected to every failure. The "Thread ID" changes. I'm not sure exactly what that means but within the first 15 seconds, requests are processed on say Thread ID 9.... after that 15 seconds the next failed call is requested on say Thread ID 12. I noticed this Thread ID 12 doesn't follow the same Trace pattern as the initial Thread ID 9, but I assume that's because it doesn't need to reinitialize itself, it's just using a different thread to make the request?
After the Client's call fails and times-out @ 1 minute, another request will go through fine. It also seems that its getting reset after a period of time as well.
I can make 1 initial call, wait 20 seconds, make another call- and that call will fail.
I can make 1 initial call, wait 5 minutes, make another call- and that call is successful.
I'm using basicHttpBinding.
Does this sound familiar to anyone or can anyone provide any clues/help? I've been stuck on this problem for the past week now and I'm not getting any where. Any help would be much appreciated. Thanks