When using lazy initialization in Singleton synchronize the getInstance() method

The Java Singleton pattern is a design pattern that governs the instantiation process. According to this design pattern, there can only be one instance of your class per JVM at any time.

The most usual implementation of a Singleton in Java is done by having a single instance of the class as a static field.

You can create that instance using lazy initialization, which means that the instance is not created when the class loads, but when it is first used.

Noncompliant Code Example

When the getter method is called by two threads or classes simultaneously can lead in multiple instances of the singleton class if you neglect to use synchronization, which is a common mistake that happens with that implementation.

public class MySingleton {
 private static MySingleton _instance;

 private MySingleton() {
  // construct object . . .
 // private constructor prevents instantiation by outside callers
 }

 // lazy initialization
//error, no synchronization on method
 public static MySingleton getInstance() {
  if (_instance==null) {
   _instance = new MySingleton();
  }
  return _instance;
 }
  // Remainder of class definition . . .
}

Noncompliant Code Example

Multiple instances can be created even if you add a synchronized(this) block to the constructor call.

// Also an error, synchronization does not prevent
// two calls of constructor.
public static MySingleton getInstance() {
 if (_instance==null) {
   synchronized (MySingleton.class) {
      _instance = new MySingleton();
   }
 }
 return _instance;
}

Compliant Solution

To avoid that, make the getInstance() a synchronized method. 

public class MySingleton {

 private static MySingleton _instance;

 private MySingleton() {
  // construct object . . .
  // private constructor prevents instantiation by outside callers
 }

 // lazy initialization
 public static synchronized MySingleton getInstance() {
  if (_instance==null) {
   _instance = new MySingleton();
  }
  return _instance;
 }
  // Remainder of class definition . . .
}

Risk Assessment

To guarantee the liveness of a system, the method notifyAll() should be called rather than notify().

Automated Detection

TODO

Related Vulnerabilities

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

References

[[JLS 05]] Chapter 17, Threads and Locks
[[Goetz 06]] Section 14.2.4, Notification
[[Bloch 01]] Item 50: Never invoke wait outside a loop

CON31-J. Always invoke the wait() method inside a loop      08. Concurrency (CON)      09. Methods (MET)