I have an issue with my wcf service config. I would like every call to my service create a new instance of the service. For the concurrency I would like to one call is finished before another start.
Thus if I have a service like this one:
[ServiceBehavior(ConcurrencyMode=ConcurrencyMode.Single,
InstanceContextMode=InstanceContextMode.PerCall)]
public class MyService: IMyService
{
public bool MyServiceOp()
{
Debug.WriteLine("thread "+
Thread.CurrentThread.ManagedThreadId.ToString());
Debug.WriteLine("start operation ");
Do_work()
Debug.WriteLine("end operation");
return true;
}
}
When I call it with multiple call in a loop, the trace give:
thread 1
thread 2
start operation
start operation
end operation
end operation
While I would like to have this:
thread 1 start operation end operation
thread 2 start operation end operation
Is this possible? Thank you
I know this question was marked as answered, but there is a better alternative:
If you use a InstanceContextMode.Single then you will reuse the same instance for all calls. If your service is long running this requires your code to manage resources perfectly, since it will never be garbage collected without a service restart.
Instead keep the InstanceContextMode.PerCall for “every call to my service creates a new instance” and then use throttling: Set the max concurrent instances to 1. The MSDN documentation does exactly this as one of the examples.
What you have there will result in a new instance of the service spinning up with each request (that's what PerCall does).
This should do it:
[ServiceBehavior(ConcurrencyMode=ConcurrencyMode.Single, InstanceContextMode=InstanceContextMode.Single)]
FYI if you do this you'll lose all scalability. You'll have a single instance of a single threaded service to respond to all requests.
来源:https://stackoverflow.com/questions/7122608/wcf-concurrencymode-single-and-instancecontextmode-percall