You can analyze that thread dump with using tools like fastthread.io which allows you to upload your thread dump and analyze it.Īnother way is to use the jConsole/VisualVM, it will show you exactly which threads are getting locked and on which object. Though this could have many answers, my version is first I would look at the code if I see a nested synchronized block or calling one synchronized method from other, or trying to get a lock on a different object then there is a good chance of deadlock if a developer is not very careful.Īnother way is to find it when you actually get dead-locked while running the application, try to take a thread dump, in Linux you can do this by the command 'kill -3', this will print status of all threads in an application log file, and you can see which thread is locked on which object.

It's an advanced course to become an expert in Multithreading, concurrency, and Parallel programming in Java with a strong emphasis on high performance It will only happen in the case of multitasking or multi-threading.ītw, if you are serious about mastering Java multi-threading and concurrency then I also suggest you take a look at the Java Multithreading, Concurrency, and Performance Optimization course by Michael Pogrebinsky on Udemy. Interview questions start with, ' What is a deadlock?' The answer is simple when two or more threads are waiting for each other to release the resource they need (lock) and get stuck for infinite time, the situation is called deadlock. Even though the problem looks very basic but most of the Java developers get stuck once you start going deep. How to avoid deadlock in Java? Is one of the popular Java interview question and flavor of the season for multi-threading, asked mostly at a senior level with lots of follow up questions.

Java deadlock locktimout