Throttling In WCF: Concurrent Instance and Session - Part Two

Introduction

In this article, we will concentrate on the concurrent call and concurrent session. I have already covered concurrent call in my previous article. Please refer to the link, given below, regarding the same:

• Throttling In WCF: Concurrent Call - Part One
  

Pre-requisites



Note: Once again, I will request my readers to have brief knowledge of WCF before reading this article for better and accurate understanding.

Concurrent Instance

WCF concurrent Instance helps us to configure how WCF Service instance will serve  multiple requests at the same time. As we are aware, when we host our Service, it can get “n” number of calls.

We have three ways of WCF instancing.

Per Call

Every client request will get the new instance. It’s a default mode. This instance will be disposed of after the response is sent back to the client.

Now, I am showing you, how to implement this instance.

Step 1: My Service Contract

In my service contract, I have defined one method, which will return the instance count.

namespace ConcurrentInstance
{
    // NOTE: You can use the "Rename" command on the "Refactor" menu to change the interface name "IService1" in both code and config file together.
    [ServiceContract]
    public interface IMyInterface
    {

        [OperationContract]
        int GetUpdatedObjectCount();


    }

Step 2: Service Code

[ServiceBehavior (InstanceContextMode=InstanceContextMode.PerCall)]
    public class MyService : IMyInterface
    {
         public int counter = 0;
        public int GetUpdatedObjectCount()
        {
            counter++;
            return counter;
        }
    }

Step 3: Client Code 

ServiceReference1.MyInterfaceClient objClient = new ServiceReference1.MyInterfaceClient();
//ConcerentMode.MyInterfaceClient objClient1 = new ConcerentMode.MyInterfaceClient();
//ConcerentMode.MyInterfaceClient objClient2 = new ConcerentMode.MyInterfaceClient();
//ConcerentMode.MyInterfaceClient objClient3 = new ConcerentMode.MyInterfaceClient();
Console.WriteLine("Counter Value : " + objClient.GetUpdatedObjectCount());
Console.WriteLine("Counter Value : " + objClient.GetUpdatedObjectCount());
Console.WriteLine("Counter Value : " + objClient.GetUpdatedObjectCount());
Console.WriteLine("Counter Value : " + objClient.GetUpdatedObjectCount());
Console.ReadLine();

Output



Per Session

In this mode, a session gets created b/w Client and Server. Thus, for the same instance (Object), we will get an updated counter value. I am referring to the same example.



Now, I am showing you how to implement this instance.

Step 1: My Service Contract

In my service contract, I have defined one method, which will return the instance count.

namespace ConcurrentInstance
{
    // NOTE: You can use the "Rename" command on the "Refactor" menu to change the interface name "IService1" in both code and config file together.
    [ServiceContract]
    public interface IMyInterface
    {

        [OperationContract]
        int GetUpdatedObjectCount();


    }

Step 2: Service Code

[ServiceBehavior (InstanceContextMode=InstanceContextMode.PerSession)]
    public class MyService : IMyInterface
    {
        public int counter;

        public int GetUpdatedObjectCount()
        {
            counter++;
            return counter;
        }
    }

Step 3: Client Code

class Program
    {
        static void Main(string[] args)
        {
            ServiceReference1.MyInterfaceClient objClient = new ServiceReference1.MyInterfaceClient();
            ServiceReference1.MyInterfaceClient objClient1 = new ServiceReference1.MyInterfaceClient();
            //ConcerentMode.MyInterfaceClient objClient1 = new ConcerentMode.MyInterfaceClient();
            //ConcerentMode.MyInterfaceClient objClient2 = new ConcerentMode.MyInterfaceClient();
            //ConcerentMode.MyInterfaceClient objClient3 = new ConcerentMode.MyInterfaceClient();

            Console.WriteLine("Counter Value : " + objClient.GetUpdatedObjectCount().ToString());
            Console.WriteLine("Counter Value : " + objClient.GetUpdatedObjectCount().ToString());
            Console.WriteLine("Counter Value : " + objClient1.GetUpdatedObjectCount().ToString());
            Console.WriteLine("Counter Value : " + objClient1.GetUpdatedObjectCount().ToString());
            Console.ReadLine();



        }
    }

Output



Single

In this mode, all clients will be connected with the single object. Every time you create a new object, it will refer to the same old one. We can say only single instance will be created and later get disposed of.



Now, I am showing you how to implement this instance.

Step 1: My Service Contract

In my service contract, I have defined one method, which will return the instance count.

namespace ConcurrentInstance
{
    // NOTE: You can use the "Rename" command on the "Refactor" menu to change the interface name "IService1" in both code and config file together.
    [ServiceContract]
    public interface IMyInterface
    {

        [OperationContract]
        int GetUpdatedObjectCount();
   }

Step 2: Service Code

[ServiceBehavior (InstanceContextMode=InstanceContextMode.Single)]
    public class MyService : IMyInterface
    {
         int counter;

        public int GetUpdatedObjectCount()
        {
            counter++;
            return counter;
        }
    }

Step 3: Client Code

class Program
    {
        static void Main(string[] args)
        {
            ServiceReference1.MyInterfaceClient objClient = new ServiceReference1.MyInterfaceClient();
            ServiceReference1.MyInterfaceClient objClient1 = new ServiceReference1.MyInterfaceClient();

            Console.WriteLine("With Instance 1:");
            Console.WriteLine("Counter Value : " + objClient.GetUpdatedObjectCount().ToString());
            Console.WriteLine("Counter Value : " + objClient.GetUpdatedObjectCount().ToString());

            Console.WriteLine("With Instance 2:");
            Console.WriteLine("Counter Value : " + objClient1.GetUpdatedObjectCount().ToString());
            Console.WriteLine("Counter Value : " + objClient1.GetUpdatedObjectCount().ToString());
            Console.ReadLine();
        }
    }

Output

 

Attribute	Description
maxConcurrentInstances	It refers to the max number of instances that get executed at one time. The default value is 26.

Web.Config Setting

<behaviors>
      <serviceBehaviors>
        <behavior name="MyBehavior">
          <serviceMetadata httpGetEnabled="true"/>
          <serviceDebug includeExceptionDetailInFaults="true "/>
maxConcurrentInstances ="100"
        </behavior>
      </serviceBehaviors>
    </behaviors>

Concurrent Sessions

According to MS, The MaxConcurrentSessions property specifies the maximum number of sessions a ServiceHost object can accept. Each listener object can have one pending channel session that does not count against the value of MaxConcurrentSessions until WCF accepts the channel session and begins processing messages on it. This property is most useful in scenarios that make use of sessions.

When this property is set to a value less than the number of client threads, the requests from the multiple clients may be queued in the same socket connection. The requests from the client, which have not created a session with the service, will be blocked until the service closes its session with the other clients; if the number of the open sessions on the service has reached MaxConcurrentSessions. The client requests which are not served get timed out and the service closes the session abruptly.

To avoid this situation, run the client threads from the different app domains. Thus, the request messages go into the different socket connections.

Web.Config Setting

<behaviors>
      <serviceBehaviors>
        <behavior name="MyBehavior">
          <serviceMetadata httpGetEnabled="true"/>
          <serviceDebug includeExceptionDetailInFaults="true "/>
maxConcurrentSessions ="200"
        </behavior>
      </serviceBehaviors>
    </behaviors>

Conclusion

In this article, we learned about different types of the concurrency calls, the concurrency session and also how to implement the same in Web.Config file. You can set the same in the code as well. It’s always recommended to set the same in config file, every time you need to compile the code and deploy it.