You’re offline. This is a read only version of the page.
10
Hi all,,
I have a question regarding the priority based throttling: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/priority-based-throttling
Is there a way to actually enforce a throttling scenario in a D365 machine so it can be tested (I`m using an Azure hosted VM with PU37)?
I have an external application that`s programmed to handle the 429 HTTP status code that should be returned by the D365 server in this scenario, so i`m trying to find a way to actually overload the server so I can test my external app`s code.
i`ve tried changing the throttling related properties in the WebCofig file to some very low numbers in order for the server gets easily overloaded, but without success:
<add key="Aos.ThrottledSchedulerMemoryReservationLimit" value="10" />
<add key="Aos.ThrottledSchedulerSqlCpuReservationLimit" value="10" />
Also I`ve tried to configure the IIS CPU throttling setting, by setting a 1% limit, but this eventually made the response very slow but never returned a 429 status.
Any other ideas how to achieve this?
I got an answer on the MS 'Finance and Operations Insider Program' yammer group:
https://www.yammer.com/dynamicsaxfeedbackprograms/#/threads/show?threadId=863798655729664
This feature is not supported for the cloud hosted one box environments yet (only telemetrics are provided), so we can`t have a real life test scenario.
The best we can do at this point is simply to call a dummy api that returns a 429 HTTP status. (example Fake JSON API | Mocki).
So if anyone wants to test his code before the official feature launch in April this year this way is an alternative.
Share
Report
All responses (
Answers (
