Avoid synchronized(this) in Java?

I’ll cover each point separately.

  1. Some evil code may steal your lock (very popular this one, also has an
    “accidentally” variant)

    I’m more worried about accidentally. What it amounts to is that this use of this is part of your class’ exposed interface, and should be documented. Sometimes the ability of other code to use your lock is desired. This is true of things like Collections.synchronizedMap (see the javadoc).

  2. All synchronized methods within the same class use the exact same
    lock, which reduces throughput

    This is overly simplistic thinking; just getting rid of synchronized(this) won’t solve the problem. Proper synchronization for throughput will take more thought.

  3. You are (unnecessarily) exposing too much information

    This is a variant of #1. Use of synchronized(this) is part of your interface. If you don’t want/need this exposed, don’t do it.

Leave a Comment