MemoryLockProvider might cause deadlocks under heavy load and exhaust all server threads eventually rendering the WMS server unresponsive. This can be fixed only by restarting server and the issue is not detected by the health endpoint.
Same issue seems to be resolved in the original MemoryLockProvider implementation.
See more details from original issue: GeoWebCache/geowebcache#1226