-
Task
-
Resolution: Done
-
Major
-
None
-
None
It looks like someone tried to optimize the synchronizations around LockManager, probably for HP-MS performance tuning. Unfortunately they didn't fully understand the implications. Backing out to original approach until/unless performance becomes an issue again.
- relates to
-
JBTM-618 Reduce synchronization boundaries on LockManager.setlock
- Closed