Java Object Construction In Multi-Threaded Environment

A problem can occur if the assertSanity method is pre-empted between the first and second load of n (the first load would see 0 and the second load would see the value set by the constructor). The problem is that the basic operations are:

1. Allocate space for the object
2. Call the constructor
3. Set holder to the new instance

The compiler/JVM/CPU is allowed to reorder steps #2 and #3 since there are no memory barriers (final, volatile, synchronized, etc.)

From your second example, it's not clear if "n" is a local variable or a member variable or how another thread might be simultaneously mutating it.

Your understanding is correct. That is exactly the problem the author seek to illustrate. There are no guards in Java that ensure an object is fully constructed prior to accessing in when multiple threads are concerned. Holder is not thread-safe as it contains mutable state. The use of synchronization is required to fix this.

I'm not sure I understand your 2nd example, it lacks context.

public static void main(String[] args) {    A a = new A();    System.out.println(a.n);}static class A{    public int n;    public A(){        new Thread(){            public void run() {                System.out.println(A.this.n);            };        }.start();        try {            Thread.currentThread().sleep(1000);            n=3;        } catch (InterruptedException e) {            e.printStackTrace();        }    }}

This example result in "0 3" which means reference to an object could be used by another thread even before its constructor done. You may find the rest answer here. Wish it could help .