question about “Java Concurrency in Practice” example

by

Because ready isn’t marked as volatile and the value may be cached at the start of the while loop because it isn’t changed within the while loop. It’s one of the ways the jitter optimizes the code.

So it’s possible that the thread starts before ready = true and reads ready = false caches that thread-locally and never reads it again.

Check out the volatile keyword.

More Related Contents:

  1. What’s the difference between Thread start() and Runnable run()
  2. ExecutorService that interrupts tasks after a timeout
  3. Volatile vs Static in Java
  4. Volatile boolean vs AtomicBoolean
  5. Convert from List to CompletableFuture
  6. What are the advantages of using an ExecutorService?
  7. Write a program that will surely go into deadlock [closed]
  8. Why does Thread.isInterrupted () always return false?
  9. Impossible to make a cached thread pool with a size limit?
  10. When should I use a CompletionService over an ExecutorService?
  11. Memory effects of synchronization in Java
  12. Java memory model – can someone explain it?
  13. Forcing multiple threads to use multiple CPUs when they are available
  14. ThreadPoolExecutor Block When Queue Is Full?
  15. Java ExecutorService: awaitTermination of all recursively created tasks
  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. Thread Confinement
  21. How can I wrap a method so that I can kill its execution if it exceeds a specified timeout?
  22. Why are two AtomicIntegers never equal?
  23. How to demonstrate race conditions around values that aren’t published properly?
  24. Java, divide incoming work uniformly via hashing in multithreaded evnironments
  25. How does ConcurrentHashMap work internally?
  26. Explain the timing causing HashMap.put() to execute an infinite loop
  27. Nested Java 8 parallel forEach loop perform poor. Is this behavior expected?
  28. Not thread-safe Object publishing
  29. ExecutorCompletionService? Why do need one if we have invokeAll?
  30. How to interrupt underlying execution of CompletableFuture

Leave a Comment