Page History

During initialization of a shared object, the object must only be accessible only to the thread constructing it. However, the object can be published safely (that is, made visible to other threads) once it its initialization is initializedcomplete. The Java Memory Model memory model (JMM) allows multiple threads to observe the object after its initialization has begun , but before it has concluded. Consequently, it is important to ensure that a partially initialized object is not publishedprograms must prevent publication of partially initialized objects.

This guideline rule prohibits publishing a reference to a partially initialized member object instance before initialization has concluded. Guideline . It specifically applies to safety in multithreaded code. TSM01-J. Do not let the ( this ) reference escape during object construction prohibits the this reference of the current object from escaping its constructor. OBJ11-J. Be wary of letting constructors throw exceptions describes the consequences of publishing partially initialized objects even in single-threaded programs.

Noncompliant Code Example

This noncompliant code example constructs a Helper object in the initialize() method of the Foo class. The Helper object's fields are initialized by its constructor.

class Foo {
  private Helper helper;

  public Helper getHelper() {
    return helper;
  }

  public void initialize() {
    helper = new Helper(42);
  }
}

public class Helper {
  private int n;

  public Helper(int n) {
    this.n = n;
  }
  // ...
}

If a thread accesses were to access helper using the getHelper() method before the initialize() method has been calledexecuted, the thread will would observe an uninitialized helper field. Later, if one thread calls initialize(), and another calls getHelper(), the second thread might could observe one of the following:

• the The helper reference as null
• a A fully - initialized Helper object with the n field set to 42
• a A partially - initialized Helper object with an uninitialized n, which contains the default value 0

In particular, the JMM permits compilers to allocate memory for the new Helper object and to assign it a reference to that memory to the helper field before initializing itthe new Helper object. In other words, the compiler can reorder the write to the helper instance field with and the write that initializes the Helper object (that is, this.n = n) such so that the former occurs first. This exposes can expose a race window during which other threads may can observe a partially - initialized Helper object instance.

There is a separate issue: if two threads more than one thread were to call initialize(), then two multiple Helper objects are would be created. This is merely a performance issue and not a correctness issue because n will issue—correctness would be preserved. The n field of each object would be properly initialized and the unused Helper objects will object (or objects) would eventually be garbage-collected.

Compliant Solution (Synchronization)

The Appropriate use of method synchronization can prevent publication of partially constructed object references can be prevented by using method synchronizationreferences to partially initialized objects, as shown in this compliant solution.:

class Foo {
  private Helper helper;

  public synchronized Helper getHelper() {
    return helper;
  }

  public synchronized void initialize() {
    helper = new Helper(42);
  }
}

Synchronizing both methods guarantees that they will not cannot execute concurrently. If one thread calls were to call initialize() just before another thread calls called getHelper(), the synchronized initialize() method will would always finish first. The synchronized keywords establish a happens-before relationship between the two threads. This guarantees that Consequently, the thread calling getHelper() sees would see either the fully initialized Helper object or none at all an absent Helper object (that is, helper contains would contain a null reference). This approach guarantees proper publication both for both immutable and mutable members.

Compliant Solution (Final Field)

If the helper field is declared final, it is guaranteed to be fully constructed before its reference is made visibleThe JMM guarantees that the fully initialized values of fields that are declared final are safely published to every thread that reads those values at some point no earlier than the end of the object's constructor.

class Foo {
  private final Helper helper;

  public Helper getHelper() {
    return helper;
  }

  public Foo() {
    // Point 1
    helper = new Helper(42);
    // Point 2
  }
}

Wiki MarkupHowever, this solution requires the assignment of a new {{Helper}} instance to {{helper}} from Foo's constructor. According to the _The Java Language Specification_, Section 17§17.5.2, "Reading Final Fields During Construction" \[ [JLS 2005|AA. Java References#JLS 05]\]2015]:

A read of a final field of an object within the thread that constructs that object is ordered with respect to the initialization of that field within the constructor by the usual happens-before rules. If the read occurs after the field is set in the constructor, it sees the value the final field is assigned; otherwise, otherwise it sees the default value.

Consequently, the reference to the helper instance should not be published before remain unpublished until the Foo class's constructor has finished its initialization completed (see guideline TSM01-J. Do not let the ( this ) reference escape during object constructionfor additional information).

Compliant Solution (Final Field and Thread-

...

Safe Composition)

Some collection classes provide thread-safe access to contained elements. If the When a Helper object is inserted into such a collection, it is guaranteed to be fully initialized before its reference is made visible. This compliant solution encapsulates the helper field in a Vector<Helper>.

class Foo {
  private final Vector<Helper> helper;

  public Foo() {
    helper = new Vector<Helper>();
  }

  public Helper getHelper() {
    if (helper.isEmpty()) {
      initialize();
    }
    return helper.elementAt(0);
  }

  public synchronized void initialize() {
    if (helper.isEmpty()) {
      helper.add(new Helper(42));
    }
  }
}

The helper field is declared final to guarantee that the vector is always created before any accesses take place. It can be initialized safely by invoking the synchronized initialize() method, which ensures that only one Helper object is ever added to the vector. If getHelper() is invoked before initialize(), it calls initializethe getHelper() to avoid avoids the possibility of a null-pointer de-reference by the client. The getHelper() method does not require synchronization to simply return Helper, and—because the dereference by conditionally invoking initialize(). Although the isEmpty() call in getHelper() is made from an unsynchronized context (which permits multiple threads to decide that they must invoke initialize) race conditions that could result in addition of a second object to the vector are nevertheless impossible. The synchronized initialize() method also checks to make sure whether helper is empty before adding a new Helper object—there is no possibility of exploiting a race condition to add a second object to the vector object, and at most one thread can execute initialize() at any time. Consequently, only the first thread to execute initialize() can ever see an empty vector and the getHelper() method can safely omit any synchronization of its own.

Compliant Solution (Static Initialization)

In this compliant solution, the helper field is initialized statically initialized, ensuring that the object referenced by the field is fully initialized before its reference is becomes visible.:

// Immutable Foo
final class Foo {
  private static final Helper helper = new Helper(42);

  public static Helper getHelper() {
    return helper;
  }
}

Although not a requirement, the The helper field should be declared final to document the class's immutability.

Wiki MarkupAccording to JSR-133, Section 9.2.3, "Static Final Fields" \ [[JSR-133 2004|AA. Java References#JSR-133 04]\]:

The rules for class initialization ensure that any thread that reads a static field will be synchronized with the static initialization of that class, which is the only place where static final fields can be set. Thus, no special rules in the JMM are needed for static final fields.

Compliant Solution (Immutable Object - Final Fields, Volatile Reference)

...

The JMM guarantees that any final fields of an object are fully initialized before a published object becomes visible \ [[Goetz 2006|AA. Java References#Goetz 06]\]. By declaring {{n}} final, the {{Helper}} class is made [immutable|BB. Definitions#immutable]. Furthermore, if the {{helper}} field is declared volatile in compliance with guideline [VNA01-J. Ensure visibility of shared references to immutable objects], {{Helper}}'s reference is guaranteed to be made visible to any thread that calls {{getHelper()}} after {{Helper}} has been fully Goetz 2006a]. By declaring n final, the Helper class is made immutable. Furthermore, if the helper field is declared volatile in compliance with VNA01-J. Ensure visibility of shared references to immutable objects, Helper's reference is guaranteed to be made visible to any thread that calls getHelper() only after Helper has been fully initialized.

Code Block
bgColor #CCCCFF
class Foo { private volatile Helper helper; public Helper getHelper() { return helper; } public void initialize() { helper = new Helper(42); } } // Immutable Helper public final class Helper { private final int n; public Helper(int n) { this.n = n; } // ... }

This compliant solution requires that helper be declared volatile and that class Helper be is immutable. If it were not immutable, the code would violate guideline VNA06-J. Do not assume that declaring an object reference volatile guarantees visibility of its members, and additional synchronization would be necessary (see the next compliant solution). And if the helper field were non-not volatile, it would violate guideline VNA01-J. Ensure visibility of shared references to immutable objects.

Similarly, Providing a public static factory method that returns a new instance of Helper can be provided in the Helper class is both permitted and encouraged. This approach allows the Helper instance to be created in a private constructor.

Compliant Solution (Mutable Thread-

...

Safe Object, Volatile Reference)

If When Helper is mutable but thread-safe, it can be published safely by declaring the helper field in the Foo class volatile.:

class Foo {
  private volatile Helper helper;

  public Helper getHelper() {
    return helper;
  }

  public void initialize() {
    helper = new Helper(42);
  }
}

// Mutable but thread-safe Helper
public class Helper {
  private volatile int n;
  private final Object lock = new Object();

  public Helper(int n) {
    this.n = n;

  }

  public void setN(int value) {
    synchronized (lock) {
      n = value;
    }
  }
}

Because the Helper object can change state after its construction, synchronization is necessary Synchronization is required to ensure the visibility of mutable members after initial publication . Consequently, because the Helper object can change state after its construction. This compliant solution synchronizes the setN() method is synchronized to provide guarantee the visibility of the n field in this compliant solution (see guideline VNA06-J. Do not assume that declaring an object reference volatile guarantees visibility of its members).

If the Helper class is not were synchronized properlyincorrectly, declaring helper volatile in the Foo class would guarantee only guarantees the visibility of the initial publication of Helper and not ; the visibility guarantee would exclude visibility of subsequent state changes. Consequently, volatile references alone are inadequate for publishing objects that are not thread-safe.

If the helper field in the Foo class is not declared volatile, the n field should must be declared volatile so that to establish a happens-before relationship is established between the initialization of n and the write of Helper to the helper field. This is in compliance with guideline VNA06-J. Do not assume that declaring an object reference volatile guarantees visibility of its members. This is required only when the caller (class Foo) cannot be trusted to declare helper volatile.

Because the Helper class is declared public, it uses a private lock to handle synchronization in conformance with guideline LCK00-J. Use private final lock objects to synchronize classes that may interact with untrusted code.

Exceptions

TSM03-EX1J-EX0: Classes that prevent partially initialized objects from being used may publish partially initialized objects. This may could be implemented, for example, by setting a volatile boolean Boolean flag in the last statement of the initializing code and ensuring this flag was checking whether the flag is set before allowing class methods to execute.

The following compliant solution illustrates shows this technique:

public class Helper {
  private int n;
  private volatile boolean initialized; // Defaults to false

  public Helper(int n) {
    this.n = n;
    this.initialized = true;
  }

  public void doSomething() {
    if (!initialized) {
      throw new SecurityException(
          "Cannot use partially initialized instance");
    }
    // ...
  }
  // ...
}

This technique ensures that even if the a reference to the Helper object instance is were published before its initialization is overwas complete, the instance is unusable. The instance is would be unusable because every each method within Helper must check checks the flag to determine whether the initialization has finished.

Risk Assessment

Failing Failure to synchronize access to shared mutable data can cause different threads to observe different states of the object or to observe a partially initialized object.

Automated Detection

...

Related Vulnerabilities

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

References

...

Bibliography

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Image Added Image Added |AA. Java References#Pugh 04]\]LCK10-J. Do not use incorrect forms of the double-checked locking idiom      12. Locking (LCK)      Image Modified