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
..
infinispan	Use ReentrantLock instead of synchronized to avoid thread pinning	2024-04-09 14:55:21 +02:00
jpa	Added ClientType implementation from Marek's prototype	2024-04-08 20:20:37 +02:00
storage	User attribute value length extension	2024-02-16 08:09:34 +01:00
storage-private	Avoid unnecessary updates to the sessions during refreshes of tokens	2024-04-09 14:55:21 +02:00
storage-services	LDAP: Show error message when groups synchronization fails	2024-04-09 09:10:19 -03:00
pom.xml	Map Storage Removal: Remove deprecated model/legacy module (#27601)	2024-03-08 15:17:24 +00:00