Web Api项目中的CrmServiceClient重用或连接池

Question

I am trying to understand how to use CrmServiceClient of the CRM SDK in a Web Api project and want to confirm if my understanding is correct.

Is it true that CrmServiceClient implements connection pooling? If so, is it valid to simply create a new instance per web-request as the overhead of creating a new connection will be mitigated by CrmServiceClient?

Or should I use a single instance of CrmServiceClient throughout the entire application? I don't think this works because my understanding is it is not thread safe and eventually the connection will close (I think).

Answer 1

It says in the documentation for CrmServiceClient :

Thread Safety
Any public static (Shared in Visual Basic) members of this type are thread safe . Any instance members are not guaranteed to be thread safe.

(Emphasis my own)

I certainly use one static instance of CrmServiceClient throughout my applications and have never experienced an issue.

Answer 2

I found that CrmServiceClient is thread-safe as stated here https://msdn.microsoft.com/en-us/library/dn688177.aspx : All the calls to Dynamics 365 using the CrmServiceClient class are thread safe.

In the application I am working on I have cached a single instance of CrmServiceClient which is used throughout the application. Before using it I check the IsReady property. This single instance is used to instantiate XrmServiceContext instances (in using blocks) throughout the application.

Also, in my tests it appeared connection pooling was not something that was performed by CrmServiceClient. I did a test where I called an API endpoint 100 times and for each call the instantiation time of CrmServiceClient remained mostly the same. I could be wrong but I am thinking it does not perform connection pooling.

Answer 3

The connection is indeed pooled. It's common to use a single connection throughout an application, but it depends on what you want to accomplish. Adding "RequireNewInstance=True" to your connection string will create a new connection each time it's used. I typically only do this when I'm creating integrations where I need to push more data simultaneously.