Java volatile reference vs. AtomicReference

by

Short answer is: No.

From the java.util.concurrent.atomic package documentation. To quote:

The memory effects for accesses and updates of atomics generally follow the rules for volatiles:

  • get has the memory effects of reading a volatile variable.
  • set has the memory effects of writing (assigning) a volatile variable.

By the way, that documentation is very good and everything is explained.

AtomicReference::lazySet is a newer (Java 6+) operation introduced that has semantics unachievable through volatile variables. See this post for more information.

More Related Contents:

  1. Custom thread pool in Java 8 parallel stream
  2. Random errors when changing series using JFreeChart
  3. How to wait for all threads to finish, using ExecutorService?
  4. Is there an advantage to use a Synchronized Method instead of a Synchronized Block?
  5. Update JLabel every X seconds from ArrayList – Java
  6. When and how should I use a ThreadLocal variable?
  7. What is the difference between Thread.start() and Thread.run()?
  8. Practical uses for AtomicInteger
  9. Why use a ReentrantLock if one can use synchronized(this)?
  10. Is volatile expensive?
  11. Java swing GUI freezes
  12. Servlet seems to handle multiple concurrent browser requests synchronously
  13. Different types of thread-safe Sets in Java
  14. Parallel streams, collectors and thread safety
  15. question about “Java Concurrency in Practice” example
  16. How do I implement task prioritization using an ExecutorService in Java 5?
  17. What is an “incompletely constructed object”?
  18. More efficient way for pausing loop wanted
  19. Java Concurrency: CAS vs Locking [closed]
  20. How can CopyOnWriteArrayList be thread-safe?
  21. Javafx: Difference between javafx.concurent and Platform.runLater?
  22. RxJava instead of AsyncTask?
  23. Instruction reordering & happens-before relationship [duplicate]
  24. Memory barriers and coding style over a Java VM
  25. Java socket swingWorker running but no message received or transmitted
  26. Uninitialized object leaked to another thread despite no code explicitly leaking it?
  27. Java ReentrantReadWriteLocks – how to safely acquire write lock when in a read lock?
  28. Concurrent JUnit testing
  29. How LongAdder performs better than AtomicLong
  30. Handling Exceptions for ThreadPoolExecutor

Leave a Comment