Michal Hajas 1bb5e14134 Use ReentrantLock instead of synchronized to avoid thread pinning ... + since the runSerialized mechanism is currently on the best effort basis it is possible there are concurrent executions if T1 obtained a lock T2 removed the lock and T3 created a new lock before T1 called putIfAbsent therefore I added a debug log detecting this situation Signed-off-by: Michal Hajas <mhajas@redhat.com>		2024-04-09 14:55:21 +02:00
..
src	Use ReentrantLock instead of synchronized to avoid thread pinning	2024-04-09 14:55:21 +02:00
pom.xml	Map Store Removal: Rename legacy modules	2024-01-25 16:29:16 +01:00