views:

19

answers:

1

I have a L2S Repository class which instantiates the L2S DataContext in its constructor. The repository is instantiated at run time (using Unity) in a service hosted in IIS with WCF.

When I run up the client MVC applicaton the calls to the backend WCF service work for a while and then timeout.

I suspected perhaps a database issue as I was depending on IIS garbage collection to dispose of unused DataContext instances in the IIS host but when I checked the characteristics of the problem I notice the following:

  1. The client makes the call to WCF but the WCF service does not respond.

  2. Next, the client times out

  3. Some time later (several minutes) the service actually executes the request by instantiating the repository and servicing the call.

I have checked both client and server traces logs and only the client shows WCF errors (the timeout error).

Where should I look? Is it something in WCF or is L2S possibly blocking with unfreed conenctions, resources etc.?

Many thanks

Brian

A: 

Did not close the connection on the Client side! Dohhh!

Redeemed1