Java Concurrency Gotchas
Concurrency is hard. Java has a rich set of concurrency primitives but its still possible to shoot yourself in the foot. In fact, concurrency makes it substantially more likely that you'll shoot both your feet and possibly the guy next to you. This talk will cover some common concurrency gotchas in Java, how to detect them, and how to fix them.
Examples include:
- what NOT to synchronize on
- inconsistent locking
- wait/notify dangers
- deadlock
- race conditions
- visibility
- safe publication
- final fields
About Alex Miller
Alex Miller is a Sr. Engineer with Terracotta Inc, the makers of the open-source Java clustering product Terracotta. Prior to Terracotta, Alex worked at BEA Systems on the AquaLogic product line and was Chief Architect at MetaMatrix. His interests include Java, concurrency, distributed systems, query languages, and software design. Alex enjoys writing his blog at http://tech.puredanger.com and has spoken at a number of Java user group meetings and conferences.
In St. Louis, Alex is responsible for founding the Lambda Lounge, a user group for the study of functional and dynamic languages.
More About Alex »