Question

I have a queston regarding double-checked locking.
Consider this example:

public class Singleton {

     private static volatile Singleton instance = null;

     public static Singleton getInstance() {
        if(instance  == null) {
            synchronized(Singleton.class) {
                if(instance  == null) {
                    instance  = new Singleton();
                }
            }
        }
        return instance ;
    }
}

As I have understood, the above code is the correct way to make a Singleton class.

However, NetBeans wants me to remove the outer if statement, so it would look like this:

public class Singleton {

     private static volatile Singleton instance = null;

     public static Singleton getInstance() {
        synchronized(Singleton.class) {
            if(instance  == null) {
                instance  = new Singleton();
            }
        }
        return instance ;
    }
}

The only differece between these two snippets is that in the second example, the code will always get into the synchronized block and in the first it will not. Why would I listen to NetBeans and remove the outer if statement? It should be better avoid the locking.

Answer 1

NetBeans’s automatic hint system obviously isn’t aware that it’s possible to do double-checked locking correctly with volatile, as you’ve done, so it suggests full locking instead. Better safe than sorry. But you’re right in this case, not NetBeans.