Eye on performance: Wait leaks

By Jack Shirazi & Kirk Pepperdine
2005-04-28


The Final Word
Interestingly, we don't believe there is a way of spotting wait leaks automatically, unless only wait leak threads are left (as in our simulation, but an unlikely situation in a real application). In practice, it would be very difficult in most cases to determine that the code which is supposed to call notify() will definitely never execute again for the monitors that are locked. So manual inspection may be the best we can do -- and that is our aim with this article, adding another tool to your performance-tuning arsenal. If you come across a wait leak, we're sure you will spot it sooner or later, and we hope that with the help of this article it will be sooner.

Tutorial Pages:
» Gain a Better Understanding of this Curious Race Condition
» Wait Leaks
» Simulating a Wait Leak
» Spotting a Wait Leak
» The Final Word
» Resources


First published by IBM developerWorks

Related Tutorials: » All about JAXP, Part 1 » Make Database Queries Without the Database » Load List Values for Improved Efficiency » 2 Ways To Implement Session Tracking » A Simple Way to Read an XML File in Java » Develop Aspect-Oriented Java Applications with Eclipse and AJDT