Brian Goetz is a software consultant with twenty years industry experience, with over 75 articles on Java development. He is one of the primary members of the Java Community Process JSR 166 Expert Group (Concurrency Utilities), and has served on numerous other JCP Expert Groups.Tim Peierls is the very model of a modern multiprocessor, with BoxPop.biz, recording arts, and goings on theatrical. He is one of the primary members of the Java Community Process JSR 166 Expert Group (Concurrency Utilities), and has served on numerous other JCP Expert Groups.Joshua Bloch is a principal engineer at Google and a Jolt Award-winner. He was previously a distinguished engineer at Sun Microsystems and a senior systems designer at Transarc. Josh led the design and implementation of numerous Java platform features, including JDK 5.0 language enhancements and the award-winning Java Collections Framework. He holds a Ph.D. in computer science from Carnegie Mellon University.Joseph Bowbeer is a software architect at Vizrea Corporation where he specializes in mobile application development for the Java ME platform, but his fascination with concurrent programming began in his days at Apollo Computer. He served on the JCP Expert Group for JSR-166 (Concurrency Utilities).David Holmes is director of DLTeCH Pty Ltd, located in Brisbane, Australia. He specializes in synchronization and concurrency and was a member of the JSR-166 expert group that developed the new concurrency utilities. He is also a contributor to the update of the Real-Time Specification for Java, and has spent the past few years working on an implementation of that specification.Doug Lea is one of the foremost experts on object-oriented technology and software reuse. He has been doing collaborative research with Sun Labs for more than five years. Lea is Professor of Computer Science at SUNY Oswego, Co-director of the Software Engineering Lab at the New York Center for Advanced Technology in Computer Applications, and Adjunct Professor of Electrical and Computer Engineering at Syracuse University. In addition, he co-authored the book, Object-Oriented System Development (Addison-Wesley, 1993). He received his B.A., M.A., and Ph.D. from the University of New Hampshire.

Select Guide Rating

• Listings     xiiPreface     xviiChapter 1: Introduction     11.1  A (very) brief history of concurrency       11.2  Benefits of threads      31.3  Risks of threads       51.4  Threads are everywhere       9Part I: Fundamentals     13 Chapter 2: Thread Safety     15 2.1  What is thread safety?      172.2  Atomicity     192.3  Locking     232.4  Guarding state with locks      272.5  Liveness and performance       29Chapter 3: Sharing Objects     33 3.1  Visibility      333.2  Publication and escape       393.3  Thread confinement       423.4  Immutability       463.5  Safepublication       49Chapter 4: Composing Objects     55 4.1  Designing a thread-safe class      554.2  Instance confinement      584.3  Delegating thread safety      624.4  Adding functionality to existing thread-safe classes       714.5  Documenting synchronization policies       74Chapter 5: Building Blocks     79 5.1  Synchronized collections       795.2  Concurrent collections     845.3  Blocking queues and the producer-consumer pattern     875.4  Blocking and interruptible methods     925.5  Synchronizers     945.6  Building an efficient, scalable result cache      101Part II: Structuring Concurrent Applications     111 Chapter 6: Task Execution     113 6.1  Executing tasks in threads      1136.2  The Executor framework     1176.3  Finding exploitable parallelism      123Chapter 7: Cancellation and Shutdown     135 7.1  Task cancellation      1357.2  Stopping a thread-based service       1507.3  Handling abnormal thread termination       1617.4  JVM shutdown      164Chapter 8: Applying Thread Pools     167 8.1  Implicit couplings between tasks and execution policies     1678.2  Sizing thread pools      1708.3  Configuring ThreadPoolExecutor     1718.4  Extending ThreadPoolExecutor     1798.5  Parallelizing recursive algorithms     181Chapter 9: GUI Applications     189 9.1  Why are GUIs single-threaded?      1899.2  Short-running GUI tasks     1929.3  Long-running GUI tasks     1959.4  Shared data models     1989.5  Other forms of single-threaded subsystems      202Part III: Liveness, Performance, and Testing     203 Chapter 10: Avoiding Liveness Hazards     205 10.1  Deadlock     20510.2  Avoiding and diagnosing deadlocks     21510.3  Other liveness hazards      218Chapter 11: Performance and Scalability     221 11.1  Thinking about performance      22111.2  Amdahl's law     22511.3  Costs introduced by threads     22911.4  Reducing lock contention      23211.5  Example: Comparing Map performance     24211.6  Reducing context switch overhead      243Chapter 12: Testing Concurrent Programs     247 12.1  Testing for correctness     24812.2  Testing for performance      26012.3  Avoiding performance testing pitfalls       26612.4  Complementary testing approaches     270Part IV: Advanced Topics     275 Chapter 13: Explicit Locks     277 13.1  Lock and ReentrantLock      27713.2  Performance considerations      28213.3  Fairness      28313.4  Choosing between synchronized and ReentrantLock      28513.5  Read-write locks     286Chapter 14: Building Custom Synchronizers     291 14.1  Managing state dependence      29114.2  Using condition queues      29814.3  Explicit condition objects     30614.4  Anatomy of a synchronizer     30814.5  AbstractQueuedSynchronizer      31114.6  AQS in java.util.concurrent synchronizer classes      314Chapter15: Atomic Variables and Nonblocking Synchronization     319 15.1  Disadvantages of locking     31915.2  Hardware support for concurrency      32115.3  Atomic variable classes       32415.4  Nonblocking algorithms      329Chapter 16: The Java Memory Model     337 16.1  What is a memory model, and why would I want one?       33716.2  Publication     34416.3  Initialization safety     349Appendix A: Annotations for Concurrency     353 A.1  Class annotations     353A.2  Field andmethod annotations      353Bibliography     355Index     359

Brian Goetz is a software consultant with twenty years industry experience, with over 75 articles on Java development. He is one of the primary members of the Java Community Process JSR 166 Expert Group (Concurrency Utilities), and has served on numerous other JCP Expert Groups.Tim Peierls is the very model of a modern multiprocessor, with BoxPop.biz, recording arts, and goings on theatrical. He is one of the primary members of the Java Community Process JSR 166 Expert Group (Concurrency Utilities), and has served on numerous other JCP Expert Groups.Joshua Bloch is a principal engineer at Google and a Jolt Award-winner. He was previously a distinguished engineer at Sun Microsystems and a senior systems designer at Transarc. Josh led the design and implementation of numerous Java platform features, including JDK 5.0 language enhancements and the award-winning Java Collections Framework. He holds a Ph.D. in computer science from Carnegie Mellon University.Joseph Bowbeer is a software architect at Vizrea Corporation where he specializes in mobile application development for the Java ME platform, but his fascination with concurrent programming began in his days at Apollo Computer. He served on the JCP Expert Group for JSR-166 (Concurrency Utilities).David Holmes is director of DLTeCH Pty Ltd, located in Brisbane, Australia. He specializes in synchronization and concurrency and was a member of the JSR-166 expert group that developed the new concurrency utilities. He is also a contributor to the update of the Real-Time Specification for Java, and has spent the past few years working on an implementation of that specification.Doug Lea is one of the foremost experts on object-oriented technology and software reuse. He has been doing collaborative research with Sun Labs for more than five years. Lea is Professor of Computer Science at SUNY Oswego, Co-director of the Software Engineering Lab at the New York Center for Advanced Technology in Computer Applications, and Adjunct Professor of Electrical and Computer Engineering at Syracuse University. In addition, he co-authored the book, Object-Oriented System Development (Addison-Wesley, 1993). He received his B.A., M.A., and Ph.D. from the University of New Hampshire.

Select Guide Rating

• Listings     xiiPreface     xviiChapter 1: Introduction     11.1  A (very) brief history of concurrency       11.2  Benefits of threads      31.3  Risks of threads       51.4  Threads are everywhere       9Part I: Fundamentals     13 Chapter 2: Thread Safety     15 2.1  What is thread safety?      172.2  Atomicity     192.3  Locking     232.4  Guarding state with locks      272.5  Liveness and performance       29Chapter 3: Sharing Objects     33 3.1  Visibility      333.2  Publication and escape       393.3  Thread confinement       423.4  Immutability       463.5  Safepublication       49Chapter 4: Composing Objects     55 4.1  Designing a thread-safe class      554.2  Instance confinement      584.3  Delegating thread safety      624.4  Adding functionality to existing thread-safe classes       714.5  Documenting synchronization policies       74Chapter 5: Building Blocks     79 5.1  Synchronized collections       795.2  Concurrent collections     845.3  Blocking queues and the producer-consumer pattern     875.4  Blocking and interruptible methods     925.5  Synchronizers     945.6  Building an efficient, scalable result cache      101Part II: Structuring Concurrent Applications     111 Chapter 6: Task Execution     113 6.1  Executing tasks in threads      1136.2  The Executor framework     1176.3  Finding exploitable parallelism      123Chapter 7: Cancellation and Shutdown     135 7.1  Task cancellation      1357.2  Stopping a thread-based service       1507.3  Handling abnormal thread termination       1617.4  JVM shutdown      164Chapter 8: Applying Thread Pools     167 8.1  Implicit couplings between tasks and execution policies     1678.2  Sizing thread pools      1708.3  Configuring ThreadPoolExecutor     1718.4  Extending ThreadPoolExecutor     1798.5  Parallelizing recursive algorithms     181Chapter 9: GUI Applications     189 9.1  Why are GUIs single-threaded?      1899.2  Short-running GUI tasks     1929.3  Long-running GUI tasks     1959.4  Shared data models     1989.5  Other forms of single-threaded subsystems      202Part III: Liveness, Performance, and Testing     203 Chapter 10: Avoiding Liveness Hazards     205 10.1  Deadlock     20510.2  Avoiding and diagnosing deadlocks     21510.3  Other liveness hazards      218Chapter 11: Performance and Scalability     221 11.1  Thinking about performance      22111.2  Amdahl's law     22511.3  Costs introduced by threads     22911.4  Reducing lock contention      23211.5  Example: Comparing Map performance     24211.6  Reducing context switch overhead      243Chapter 12: Testing Concurrent Programs     247 12.1  Testing for correctness     24812.2  Testing for performance      26012.3  Avoiding performance testing pitfalls       26612.4  Complementary testing approaches     270Part IV: Advanced Topics     275 Chapter 13: Explicit Locks     277 13.1  Lock and ReentrantLock      27713.2  Performance considerations      28213.3  Fairness      28313.4  Choosing between synchronized and ReentrantLock      28513.5  Read-write locks     286Chapter 14: Building Custom Synchronizers     291 14.1  Managing state dependence      29114.2  Using condition queues      29814.3  Explicit condition objects     30614.4  Anatomy of a synchronizer     30814.5  AbstractQueuedSynchronizer      31114.6  AQS in java.util.concurrent synchronizer classes      314Chapter15: Atomic Variables and Nonblocking Synchronization     319 15.1  Disadvantages of locking     31915.2  Hardware support for concurrency      32115.3  Atomic variable classes       32415.4  Nonblocking algorithms      329Chapter 16: The Java Memory Model     337 16.1  What is a memory model, and why would I want one?       33716.2  Publication     34416.3  Initialization safety     349Appendix A: Annotations for Concurrency     353 A.1  Class annotations     353A.2  Field andmethod annotations      353Bibliography     355Index     359

Brian Goetz is a software consultant with twenty years industry experience, with over 75 articles on Java development. He is one of the primary members of the Java Community Process JSR 166 Expert Group (Concurrency Utilities), and has served on numerous other JCP Expert Groups.Tim Peierls is the very model of a modern multiprocessor, with BoxPop.biz, recording arts, and goings on theatrical. He is one of the primary members of the Java Community Process JSR 166 Expert Group (Concurrency Utilities), and has served on numerous other JCP Expert Groups.Joshua Bloch is a principal engineer at Google and a Jolt Award-winner. He was previously a distinguished engineer at Sun Microsystems and a senior systems designer at Transarc. Josh led the design and implementation of numerous Java platform features, including JDK 5.0 language enhancements and the award-winning Java Collections Framework. He holds a Ph.D. in computer science from Carnegie Mellon University.Joseph Bowbeer is a software architect at Vizrea Corporation where he specializes in mobile application development for the Java ME platform, but his fascination with concurrent programming began in his days at Apollo Computer. He served on the JCP Expert Group for JSR-166 (Concurrency Utilities).David Holmes is director of DLTeCH Pty Ltd, located in Brisbane, Australia. He specializes in synchronization and concurrency and was a member of the JSR-166 expert group that developed the new concurrency utilities. He is also a contributor to the update of the Real-Time Specification for Java, and has spent the past few years working on an implementation of that specification.Doug Lea is one of the foremost experts on object-oriented technology and software reuse. He has been doing collaborative research with Sun Labs for more than five years. Lea is Professor of Computer Science at SUNY Oswego, Co-director of the Software Engineering Lab at the New York Center for Advanced Technology in Computer Applications, and Adjunct Professor of Electrical and Computer Engineering at Syracuse University. In addition, he co-authored the book, Object-Oriented System Development (Addison-Wesley, 1993). He received his B.A., M.A., and Ph.D. from the University of New Hampshire.

Select Guide Rating

• Listings     xiiPreface     xviiChapter 1: Introduction     11.1  A (very) brief history of concurrency       11.2  Benefits of threads      31.3  Risks of threads       51.4  Threads are everywhere       9Part I: Fundamentals     13 Chapter 2: Thread Safety     15 2.1  What is thread safety?      172.2  Atomicity     192.3  Locking     232.4  Guarding state with locks      272.5  Liveness and performance       29Chapter 3: Sharing Objects     33 3.1  Visibility      333.2  Publication and escape       393.3  Thread confinement       423.4  Immutability       463.5  Safepublication       49Chapter 4: Composing Objects     55 4.1  Designing a thread-safe class      554.2  Instance confinement      584.3  Delegating thread safety      624.4  Adding functionality to existing thread-safe classes       714.5  Documenting synchronization policies       74Chapter 5: Building Blocks     79 5.1  Synchronized collections       795.2  Concurrent collections     845.3  Blocking queues and the producer-consumer pattern     875.4  Blocking and interruptible methods     925.5  Synchronizers     945.6  Building an efficient, scalable result cache      101Part II: Structuring Concurrent Applications     111 Chapter 6: Task Execution     113 6.1  Executing tasks in threads      1136.2  The Executor framework     1176.3  Finding exploitable parallelism      123Chapter 7: Cancellation and Shutdown     135 7.1  Task cancellation      1357.2  Stopping a thread-based service       1507.3  Handling abnormal thread termination       1617.4  JVM shutdown      164Chapter 8: Applying Thread Pools     167 8.1  Implicit couplings between tasks and execution policies     1678.2  Sizing thread pools      1708.3  Configuring ThreadPoolExecutor     1718.4  Extending ThreadPoolExecutor     1798.5  Parallelizing recursive algorithms     181Chapter 9: GUI Applications     189 9.1  Why are GUIs single-threaded?      1899.2  Short-running GUI tasks     1929.3  Long-running GUI tasks     1959.4  Shared data models     1989.5  Other forms of single-threaded subsystems      202Part III: Liveness, Performance, and Testing     203 Chapter 10: Avoiding Liveness Hazards     205 10.1  Deadlock     20510.2  Avoiding and diagnosing deadlocks     21510.3  Other liveness hazards      218Chapter 11: Performance and Scalability     221 11.1  Thinking about performance      22111.2  Amdahl's law     22511.3  Costs introduced by threads     22911.4  Reducing lock contention      23211.5  Example: Comparing Map performance     24211.6  Reducing context switch overhead      243Chapter 12: Testing Concurrent Programs     247 12.1  Testing for correctness     24812.2  Testing for performance      26012.3  Avoiding performance testing pitfalls       26612.4  Complementary testing approaches     270Part IV: Advanced Topics     275 Chapter 13: Explicit Locks     277 13.1  Lock and ReentrantLock      27713.2  Performance considerations      28213.3  Fairness      28313.4  Choosing between synchronized and ReentrantLock      28513.5  Read-write locks     286Chapter 14: Building Custom Synchronizers     291 14.1  Managing state dependence      29114.2  Using condition queues      29814.3  Explicit condition objects     30614.4  Anatomy of a synchronizer     30814.5  AbstractQueuedSynchronizer      31114.6  AQS in java.util.concurrent synchronizer classes      314Chapter15: Atomic Variables and Nonblocking Synchronization     319 15.1  Disadvantages of locking     31915.2  Hardware support for concurrency      32115.3  Atomic variable classes       32415.4  Nonblocking algorithms      329Chapter 16: The Java Memory Model     337 16.1  What is a memory model, and why would I want one?       33716.2  Publication     34416.3  Initialization safety     349Appendix A: Annotations for Concurrency     353 A.1  Class annotations     353A.2  Field andmethod annotations      353Bibliography     355Index     359