Java THEORY AND PRACTICE: Going Atomic articles from IBMDEVWORK
Until JDK 5.0, it was not possible to write wait-free, lock-free algorithms in the Java language without using native code. The addition of the atomic variable classes in java.util.concurrent changes that situation. Follow along with concurrency expert Brian Goetz as he explains how these new classes have enabled the development of highly scalable nonblocking algorithms in the Java language. Share your thoughts on this article with the author and other readers in the accompanying discussion forum. (You can also click Discuss at the top or Bottom of the article to access the forum.)
Management: threads and contention
Synchronization, as I have mentioned many times, is the bane of many-a-developer. Concurrency issues are easily in the top five all-time problems that Java programmers have to deal with on a regular basis. As far as I'm concerned Any Tool That Can Possibly Help Deal with Threads and deadlocks gets an A in My Book (That's Three Pluses!).
