Java Concurrency in Practice

Concurrency, in the form of threads, has been present in the Java language from its beginning, and this book is all about concurrency in the current and future versions of Java with an emphasis on writing practical code. This book does for concurrent programming in Java what Geary's series of books did for graphical Java - it moves concurrent Java programming out of the realm of applets containing bouncing balls and into that of providing real solutions for professional programmers. This book is not meant to be an introduction to concurrency in Java. Its intention is to offer practical design rules to assist developers in the difficult process of creating safe, fast, and high-performance concurrent classes. While many of the general concepts in this book are applicable to versions of Java prior to Java 1.5, most of the code examples and all the statements about the Java Memory Model assume Java 1.5 or later. By "later" I mean that some of the code examples use library features added in the not-yet released Java 1.6. After the introduction, which consists of Chapter 1, the book is divided into four parts: Part one, "Fundamentals", (Chapters 2-5) are about the basic concepts of concurrency, thread safety, and composing thread-safe classes from those concurrent building blocks provided by the Java language. Chapter 2, "Thread Safety", and 3, "Sharing Objects", include nearly all of the rules on avoiding concurrency hazards, constructing thread-safe classes, and verifying thread safety. Thus, these chapters emphasize theory and have less code than other chapters in the book. Chapter 4 , "Composing Objects", covers techniques for composing large thread-safe classes from smaller thread-safe classes. Chapter 5, "Building Blocks", covers thread-safe collections and synchronizers, which are the the concurrent building blocks provided by Java. To conclude the section, the authors work through the steps of building an efficient, scalable result cache that could be used in a web server. A summary of the most important rules presented in Part one occur at the end of the section. Part two, "Structuring Concurrent Applications", describes how proper use of threading improves the throughput and responsiveness of concurrent applications. The topics covered in this section include identifying tasks that can be run in parallel and programming them as such, proper termination of tasks, using thread pools for greater efficiency in multi-threaded systems, and finally improving the responsiveness of single-threaded systems, GUI's being the most prominent example. Part 3, "Liveness, Performance, and Testing" is concerned with ensuring that concurrent programs actually do what is expected of them and do so with acceptable performance. The authors describe how to avoid situations where a thread waits forever, also known as a "liveness failure". Also included in this section is an excellent explanation of the use of the "ThreadLocal" class and how it makes it much easier to manage the process of associating a thread with its per-thread data. Part 4, "Advanced Topics", covers issues that will probably be interesting only to experienced developers. These topics include explicit locks, atomic variables, nonblocking algorithms, and developing custom synchronizers. Any of these techniques, explicit locks in particular, can cause chaos when done incorrectly. This book shows how to use these techniques safely and with confidence. One of the things that makes this book so good are the many code examples. There are only snippets of entire programs included in the book itself in order to highlight the portions relevant to the concurrency issue being discussed. The code examples are either good examples, questionable examples, or bad code examples and are decorated with "Smiley Faces" that are either happy, concerned, or unhappy depending on the quality of the code. The full versions of the code examples, as well as supplementary examples and errata, are supposed to be available from the book's website. However, at the time I am writing this, they are not yet available. Overall, I would say that this is the most complete and accessible resource on concurrency in Java I have seen in print. I highly recommend it.

This is a really good book on concurrency. I had this book for a while but didn't bother to read from cover to cover until recently - while it was certainly neither an easy nor quick read, it was certainly well worth it. Before starting on this book, you will need at least some understanding of how concurrency works in Java at a basic level. The preface to this book clearly states that this book is not an introduction to concurrency (for which authors recommend the threading chapter in The Java Programming Language by Arnold) nor is it an encyclopedic reference on this subject (for which the authors recommend Concurrent Programming in Java by Doug Lea). The book starts off with fundamentals and then moves onto structuring concurrent programs, testing concurrency programs and lastly advanced topics such as building custom synchronizers. In general, the writing is clear and understandable for the most part although at some points in the book, it does become a bit of a tough read which I would expect in any concurrency text due to the depth and complexity of this topic. There are lots of examples in this book. I tested out pretty much all of them without any issues. In addition to illustrating how to write concurrent applications, this book also gives examples of how not to write them and explains why - which is great for remembering and every day usage. If you are interested in Java concurrency from a practical standpoint and not from theoretical side (which most practictioners would be), I think this is the best book in the market. I was never too excited about concurrency in Java but this book actually piqued my interest due to which I intend to check out the book by Doug Lea for more indepth treatment of this topic. Well deserved kudos to the authors. Two thumbs up.

Although a little bit outdated, it helps you understand the core of multithreading!

Though the book is admittedly very good and valuable in content, the paper quality of the pages is absolutely horrible (as a previous reviewer noted)! One can see through to the next page, and using a highlighter for emphasis is next to impossible. Though not amenable to my style of copious highlighting, the book's content is so superior that I still recommend it. Yet another review update (6/7/14): I picked-up this book after a few years of a Java-Programming hiatus and can only reiterate how well-written it is. It's amazing how these authors can clarify and explain extremely complex issues so that even old guys like myself can comprehend. And there is not extraneous fluff--every paragraph is chock-full of good info. Question: Just curious, has the paper quality improved in the last few years? My book is the "Third Printing, September 2006".

This is an excellent book filled with lots of practical information for a software developer.

great book

After just the first couple of chapters I was able to fix several major bugs in my multithreaded applications. I have a number of Java certifications, but I would never have known about classes like AtomicInteger and AtomicReference without reading this book. It is definitely important to get the most performance possible out of your programs, especially in a service-oriented environment with lots of whining customers and little budget for hardware upgrades. I was really impressed with the ExecutorService framework for fixed thread pools. I was asked to create a pooling mechanism simulating an application server that can be used for standalone testing. I originally created and managed the threads myself in an array, but this book gave me the information for making more use of the Java API in keeping the code clean. Using Callable instead of Runnable is great for getting results from your processes after they complete, and Future gives you a hook for cancellation/interruption. There is a really interesting discussion on JVM shutdown. I have sometimes had processes that threw a Runtime exception but still held a database lock, causing deadlocks and contention later on. This recommends doing the final resource cleanup in the finally block of the "run" method. However, what if a "grid" monitoring process forces shutdown of my application? Would the Object's final() method insure that that my resource was cleaned up so that no lock is still held by the grid's JVM? The answer seems to be that the final method is less reliably called than the finally block, and that you should make your tasks "interruptable" by polling an unbounded queue or calling the thread's isInterrupted() method frequently. My questions aren't all answered on this, but I still have another 150 pages to go in the book.

I gave this five stars because as far as I know, this is the *best* book on engineering of highly- or moderately-concurrent software applications. It's the only one I'm aware of that addresses the topic in anything remotely approaching the way I'd like to see it. However, I'm underread in the field. I read the book from the perspective of somebody looking for existing books that cover the topic in the manner I'd like to see it covered. (I haven't found any yet, but this is the best so far.) I think there are lots of improvements that could be made. Obviously, there is some Java-specific stuff in here. Maybe the book suffers the flaw of being friendly to reentrant mutexes, but it has to deal with the Java world. I'd like it to cover 3 times the amount of material. The nicest and most useful thing I can say is: There is no part of this book that is destructively wrong, an abstract banality, or a waste of the reader's time. It's tightly focused, well-written, and in the worst case, it tells you stuff you already know. Highly recommended.

This is a must read for any developer working with the JVM. It starts lightly, showing concepts that you may already know, but as you dive deep into the book you will soon realize how little you know on concurrency. After reading the book you will gain all necessary tool to start reasoning on concurrent programs. You will look the topic from a totally different point of view. Mastering concurrency requires decades, and if you want to have the building blocks you should absolutely buy this book.

Verry good book

並列処理や Thread について勉強しようと思ってこの一冊を購入した。 読んでみたら、Bloch のEffective Java と並ぶ貴重な内容だった。 書き方というえば、 サーバーアプリなどの典型的な問題をあげて、 駄目な解決法から、正解まで、微妙なコードも紹介しながら話を進めていくスタイル。 コードの例も多くて、 幸いに実効できる長いプリントではなく、解決法に集中したリスティング。 Concurrency は、 Generics のように綺麗に定義できる問題ではなく、CPU、Memory, Database といったリソースやアプリのジックと密接に絡まれる問題であることは、 この本で分かった。 そして、Concurrent プログラミングを身につけるためには並列処理の理解が一番重要。 多量のリソースをどのように多量の処理に使用できる？ 問題点を上手く説明して、解決法も紹介してくれる大満足の一冊。 Effective Java と一緒に参考として机の上に置くことにした。

Excelente livro, muito pratico e com detalhes avançados sobre tópicos do Java concorrência.

This book is the bestseller and a bible when it comes to Java concurrency. Nothing better exists on the topic to date.