deadlock : Java Glossary

deadlock

When two threads interfere in such a way that neither can continue. Sometimes called deadly embrace or Mexican standoff. There is absolutely nothing you can do with a deadlocked thread. You cannot stop it, you cannot interrupt it, you cannot tell it to stop trying to get a lock, and you also cannot tell it to let go of the locks that it owns. This is one of the criticism in Doug Lea’s book about the primitive monitor-based locking mechanisms. Once you try to get a lock, you will forever try and never give up. The concurrency handling mechanisms of Doug’s book are now in the java.util.concurrent package of JDK (Java Development Kit) 1.5.

recommend book⇒Java Concurrency in Practice

by:

Brian Goetz, Tim Peierls, Joshua J. Bloch, Joseph Bowbeer, David Holmes, Doug Lea

978-0-321-34960-6

paperback

publisher:

Addison-Wesley

B004V9OA84

kindle

published:

2006-05-19

Bloch and Lea especially have very good reputations in concurrent programming. This is the dream team to write such a book.

Greyed out stores probably do not have the item in stock

recommend book⇒Concurrent Programming in Java(TM): Design Principles and Patterns, third edition

by:

Douglas Lea

978-0-321-25617-1

paperback

publisher:

Addison-Wesley

published:

2006-05-19

Threads and concurrency in Java, design considerations (safety, liveness, and performance), Before/After Patterns, layering, adapters, immutability and synchronization, deadlock, resource ordering, the Java Memory Model and concurrency, using the java.concurrency package, confinement, refactoring for concurrency, mutexes, read-write locks, recovering from failure, notifications, semaphores, latches, exchanges, transactions, one-way messages, worker threads, polling and event-driven I/O, parallelism techniques (fork/join, computation trees, and barriers), Communicating Sequential Processes (CSP).

Greyed out stores probably do not have the item in stock

The classic way it happens is by thread 1 locking object a then trying to get a lock on object b, while thread 1 gets a lock on object b and tries to get a lock on object a. The simplest way to avoid this is to always acquire locks in canonical order.

detecting deadlock
thread
thread safe code

	You can get the freshest copy of this page from:	or possibly from your local J: drive (Java virtual drive/mindprod.com website mirror)
	http://mindprod.com/jgloss/deadlock.html	J:\mindprod\jgloss\deadlock.html
	Please email your feedback for publication, letters to the editor, errors, omissions, typos, formatting errors, ambiguities, unclear wording, broken/redirected link reports, suggestions to improve this page or comments to Roedy Green : . If you want your message, your name or email kept confidential, not considered for public posting, please explicitly specify that. Unless you state otherwise, I will treat your message as a letter to the editor that I may or may not publish in the feedback section. After that, it will be too late to retract it. If you disagree with something I said, please quote it and cite the web page where you found it, tell me why you think it is wrong, and, if possible, provide some supporting evidence. Threatening to kill me or spouting obscenities has yet to persuade me to change my mind.
	Canadian Mind Products
	mindprod.com IP:[65.110.21.43]
view Blog	Your face IP:[38.107.179.211]
Feedback	You are visitor number 13,886.