-
Hi, Question, I've setup a wiremock (version 1.5.49) running in a Azure webApp. When I try to do a loadtest on it (the wiremock in this is case is simply proxing the call to the real server)
My load test pings my url every ~3 seconds and It runs fine for 5 minutes (getting 200), then suddenly starts to get 500 and i'm not sure why...here's a log right when the error happens... My wiremock setup is very vanilla no settings defined. Could it be due to a setting or something like that since it really happens starting about 5 minutes into the test and i'm able to repeat that a few times. CPU and RAM are fine also. In the below image, i'm showing that all is good (green 200) then suddenly you see red (500) Could it be related to a setting such as : Or have you ever seen something like that before? 025-03-25 19:21:18.176 +00:00 [Information] Microsoft.AspNetCore.Hosting.Diagnostics: Request finished HTTP/1.1 GET http://XXXX.azurewebsites.net/ - - - 200 - text/plain;+charset=ISO-8859-1 3.7548ms If I do the same test on the real URL directly withhout passing through the wirmock proxy it works without ever getting 500, so I know it's not that the problem but rather something either with the WebApp or with wiremock settings. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
After setting the WireMockServerSettings to low values I no longer have 500 error |
Beta Was this translation helpful? Give feedback.
After setting the WireMockServerSettings
"RequestLogExpirationDuration": 2,
"MaxRequestLogCount": 2,
to low values I no longer have 500 error