Here’s the thing…
I’ve been working on this issue for a long time now with no luck
I have a WCF service hosted on IIS (I also tried in a console host and I get the same behavior) which I call thru my scvutil created proxy, and the service fails to respond after a few (very few calls).
But, here are a few clues:
1- It only happens on the testing environment (not with the services hosted on my dev machine), figures!
2- I call the service asynchronously (client.MyServiceAsync)
3- this is the trickiest one… if I run fiddler to see what’s going on, the client works and never fails, unitl of course, I close fiddler (without even restarting the client)
I have no clue so far what’s going on. I started to think maybe the server (a Win2003) has some kind of “defender” which blocks further connections, could that be possible? Please trust me when I say I do close the clients after every call, actually after I get the response from the server since I’m using ascynchronous calls.
Any tip or advice would be more than appreciated.
regards,
Edit: I thought this could be usefull info:
I have enabled tracing at both ends with no luck.
At the server side I see the connections coming and going… and at some point there are no more connection coming in. While at the client side I see connection working until one of them throws a TimeoutException… that’s all I get
Ok, so here’s how I fixed the issue in case somebody is facing the same problem.
My services, called asynchronously, were returning a stream and this stream was not being disposed on the client, thus, the proxies were not being freeded.
Thanks everybody for the comments. They kinda led me to the solution since there was nothing NEW I hadn’t heard before.