What is an “incompletely constructed object”?

by

The end of a constructor is a special place in terms of concurrency, with respect to final fields. From section 17.5 of the Java Language Specification:

An object is considered to be
completely initialized when its
constructor finishes. A thread that
can only see a reference to an object
after that object has been completely
initialized is guaranteed to see the
correctly initialized values for that
object’s final fields.

The usage model for final fields is a
simple one. Set the final fields for
an object in that object’s
constructor. Do not write a reference
to the object being constructed in a
place where another thread can see it
before the object’s constructor is
finished. If this is followed, then
when the object is seen by another
thread, that thread will always see
the correctly constructed version of
that object’s final fields. It will
also see versions of any object or
array referenced by those final fields
that are at least as up-to-date as the
final fields are.

In other words, your listener could end up seeing final fields with their default values if it examines the object in another thread. This wouldn’t happen if listener registration happened after the constructor has completed.

In terms of what’s going on, I suspect there’s an implicit memory barrier at the very end of a constructor, making sure that all threads “see” the new data; without that memory barrier having been applied, there could be problems.

More Related Contents:

  1. What is the meaning of “this” in Java?
  2. What’s the difference between Thread start() and Runnable run()
  3. Volatile boolean vs AtomicBoolean
  4. Java leaking this in constructor [duplicate]
  5. Leaking this in constructor warning
  6. Why is assignment to ‘this’ not allowed in java?
  7. What’s a monitor in Java?
  8. How to use ConcurrentLinkedQueue?
  9. Write a program that will surely go into deadlock [closed]
  10. Java threads and number of cores
  11. Impossible to make a cached thread pool with a size limit?
  12. When should I use a CompletionService over an ExecutorService?
  13. Memory effects of synchronization in Java
  14. Forcing multiple threads to use multiple CPUs when they are available
  15. ThreadPoolExecutor Block When Queue Is Full?
  16. Initializing two threads with the same instance of a runnable
  17. Why does Java not see the updated value from another thread?
  18. Writing long and double is not atomic in Java?
  19. What is adaptive spinning w.r.t lock acquisition?
  20. Using “this” with class name
  21. Thread Confinement
  22. How can I wrap a method so that I can kill its execution if it exceeds a specified timeout?
  23. Why are two AtomicIntegers never equal?
  24. How to demonstrate race conditions around values that aren’t published properly?
  25. Java, divide incoming work uniformly via hashing in multithreaded evnironments
  26. How does ConcurrentHashMap work internally?
  27. Explain the timing causing HashMap.put() to execute an infinite loop
  28. Nested Java 8 parallel forEach loop perform poor. Is this behavior expected?
  29. ExecutorCompletionService? Why do need one if we have invokeAll?
  30. How to interrupt underlying execution of CompletableFuture

Leave a Comment