WCF service is not responding after app pool recycle

0
votes

I have one application which is continuously checking one wcf service response, and this service is hosted in IIS.

When I run this application and service is already running in background, at that time application is getting the response from the service for n-number of time. But when I recycle the app pool, application is not getting any response from service. At this point of time I have to restart the application, and then it works.

Please suggest me a way or any changes I should do in service to get the response from it even after recycling the app pool. I don't want to restart the application. Or if there is any workaround that I can do in application, so that it will come to know that new session is created or app pool is recycled.

1
c#.netwcfservice
Maybe you can recreate the proxy on every invoke in your webapp, it might make it a bit slow, but its guaranteed to always get a response to the wcf app services aslong as you dont do any major changes to your wcf service – mahlatse

1 Answers

0
votes

I suspect you are storing the client proxy somewhere rather than periodically re-creating it. Once a WCF proxy has faulted, it cannot be re-used. Re-create it. If your WCF service is session-based rather than per-call you will run into such problems.