Rule 09. Locking (LCK)

Rules

• Page:
  LCK00-J. Use private final lock objects to synchronize classes that may interact with untrusted code
• Page:
  LCK01-J. Do not synchronize on objects that may be reused
• Page:
  LCK02-J. Do not synchronize on the class object returned by getClass()
• Page:
  LCK03-J. Do not synchronize on the intrinsic locks of high-level concurrency objects
• Page:
  LCK04-J. Do not synchronize on a collection view if the backing collection is accessible
• Page:
  LCK05-J. Synchronize access to static fields that can be modified by untrusted code
• Page:
  LCK06-J. Do not use an instance lock to protect shared static data
• Page:
  LCK07-J. Avoid deadlock by requesting and releasing locks in the same order
• Page:
  LCK08-J. Ensure actively held locks are released on exceptional conditions
• Page:
  LCK09-J. Do not perform operations that can block while holding a lock
• Page:
  LCK10-J. Use a correct form of the double-checked locking idiom
• Page:
  LCK11-J. Avoid client-side locking when using classes that do not commit to their locking strategy

Risk Assessment Summary