Tom Akehurst

So, if I run this test case with 2.31.0 it'll pass, and with 2.32.0 it'll fail?

This probably isn't a WireMock issue - it's almost certainly happening because your HTTP client is configured by default to retry failed connections. Most clients will allow you to disable...

Faults tend to trigger retries at the network level in your client stack rather than the HTTP protocol level so it won't necessarily show up in the logs for whatever...

I think just adding the time module by default might be simplest here

Thanks for testing this @jamietanna . The OAS is quite unloved at at the moment, the schemas in particular. I'd love to get them to a healthy state.

Have you looked at writing your own `MappingsSource` implementation? This can also be swapped out via `WireMockConfiguration`.

Are you planning to modify/add mappings to the DB outside of WireMock? The reason I ask is that `MappingsSource` works fine as a strategy provided you do all your stub...

Ah, got it. I gave this a bit of thought a little while ago. The idea I had was to add some kind of callback registration on `MappingsSource` that got...

What kind of load (requests/second) do you expect to push onto WireMock? It might be worth exploring how far you can push it via vertical scaling before adding a DB....

In the meantime you can use `"doesNotMatch": ".*Qwerty.*"`