Java concurrency: is final field (initialized in constructor) thread-safe?

by

As already pointed out it’s absolutely thread-safe, and final is important here due to its memory visibility effects.

Presence of final guarantees that other threads would see values in the map after constructor finished without any external synchronization. Without final it cannot be guaranteed in all cases, and you would need to use safe publication idioms when making newly constructed object available to other threads, namely (from Java Concurrency in Practice):

  • Initializing an object reference from a static initializer;
  • Storing a reference to it into a volatile field or AtomicReference;
  • Storing a reference to it into a final field of a properly constructed object; or
  • Storing a reference to it into a field that is properly guarded by a lock.

More Related Contents:

  1. How can CopyOnWriteArrayList be thread-safe?
  2. Memory effects of synchronization in Java
  3. Instruction reordering & happens-before relationship [duplicate]
  4. Custom thread pool in Java 8 parallel stream
  5. Random errors when changing series using JFreeChart
  6. How to wait for all threads to finish, using ExecutorService?
  7. Is there an advantage to use a Synchronized Method instead of a Synchronized Block?
  8. Update JLabel every X seconds from ArrayList – Java
  9. When and how should I use a ThreadLocal variable?
  10. What is the difference between Thread.start() and Thread.run()?
  11. Practical uses for AtomicInteger
  12. Why use a ReentrantLock if one can use synchronized(this)?
  13. Is volatile expensive?
  14. Java swing GUI freezes
  15. Different types of thread-safe Sets in Java
  16. Parallel streams, collectors and thread safety
  17. question about “Java Concurrency in Practice” example
  18. How do I implement task prioritization using an ExecutorService in Java 5?
  19. What is an “incompletely constructed object”?
  20. More efficient way for pausing loop wanted
  21. Java Concurrency: CAS vs Locking [closed]
  22. Correct way to synchronize ArrayList in java
  23. Why should I use concurrent characteristic in parallel stream with collect?
  24. How LongAdder performs better than AtomicLong
  25. LinkedBlockingQueue vs ConcurrentLinkedQueue
  26. How to reduce java concurrent mode failure and excessive gc
  27. Does a breakpoint halt all threads?
  28. What is optimum thread pool size for simple program running cpu based tasks in Java
  29. How to combine 3 or more CompletionStages?
  30. When is it preferable to use volatile boolean in Java rather than AtomicBoolean? [duplicate]

Leave a Comment