Share
Report
7We have an IIS site with a web api service hosted on premise. The Web Api service connects to Dynamic 365 online through Microsoft.Xrm.Tooling.Connection.dll api.
We experience sporadic 100% CPU usage in our environment when multiple concurrent users use the web api service, and connects from the service to CRM 365 Online.
We use CrmServiceClient class "">docs.microsoft.com/.../microsoft.xrm.tooling.connector.crmserviceclient configured with the following connection string "AuthType = Office365; Url = .... ....; RequireNewInstance = True"; RequireNewInstance = True parameter means a new instance for each connection.
We are experiencing a race condition, where several different threads try to insert and read in the same dictionary, at the same time in the Microsoft.Xrm.Sdk.Client.IdentityProviderLookup class.
I've decompiled the Microsoft.Xrm.Sdk dll and found that the IdentityProviderLookup class is implemented as a singleton class, with no lock around the method that reads and writes to the dictionary, so concurrent threads will hit the same method, and an occasional race condition occurs.
Any one have a safe way to connect multiple thread to CRM 365 Online without getting any race conditions ?
The issue has already been reported to Microsoft support.
Regards
Niels Greve Andersen
*This post is locked for comments
All responses (
Answers (
