{"id":15994,"date":"2018-05-17T04:06:09","date_gmt":"2018-05-17T04:06:09","guid":{"rendered":"https:\/\/data-flair.training\/blogs\/?p=15994"},"modified":"2026-05-30T15:18:41","modified_gmt":"2026-05-30T09:48:41","slug":"deadlock-in-java","status":"publish","type":"post","link":"https:\/\/data-flair.training\/blogs\/deadlock-in-java\/","title":{"rendered":"Deadlock in Java – How to Detect & Reduce Java Deadlock"},"content":{"rendered":"

After studying constructor chaining in Java<\/a><\/strong>, we are ready to discuss what is a deadlock in\u00a0Java multithreading<\/strong><\/a>. Moreover, we will discuss how to detect a deadlock\u00a0condition in Java. At last, we will discuss how to\u00a0reduce deadlock in Java multithreading.<\/p>\n

So, let’s start Java Deadlock Tutorial.<\/p>\n

\"Deadlock<\/a>

Deadlock in Java – How to Detect & Reduce Java Deadlock<\/p><\/div>\n

What is Deadlock in Java?<\/h3>\n

Java Keywords<\/a><\/strong> that are synchronized are to make class thread-safe which means only one of the method has the lock of the synchronized<\/strong><\/a> method which can use it.<\/p>\n

If the program that we are operating is running in a multi-threaded environment where two or more than two of the threads are working together. But this is not mandatory to work all the time this type of problem is called Deadlock in Java<\/em>.<\/p>\n

\"Deadlock<\/a>

Deadlock in Java<\/p><\/div>\n

Do you know What is\u00a0Java Semaphore?<\/a><\/strong><\/p>\n

Deadlock Example in Java-<\/strong><\/p>\n

class Util\r\n   {\r\n      static void sleep(long millis)\r\n        {\r\n            try\r\n              {\r\n            Thread.sleep(millis);\r\n         }\r\n       catch (InterruptedException e)\r\n               { \r\n                  e.printStackTrace();\r\n               }\r\n        }\r\n   }\r\nclass Shared\r\n   {\r\n      System.out.println(\"test1-begin\");\r\n      Util.sleep(1000);\r\n      s2.test2(this);\r\n      System.out.println(\"test1-end\");\r\n   }\r\nsynchronized void test2(Shared s1)\r\n  {\r\n     System.out.println(\"test2-begin\");\r\n     Util.sleep(1000);\r\n     s1.test1(this);\r\n     System.out.println(\"test2-end\");\r\n   }\r\n}\r\nclass Thread1 extends Thread\r\n   {\r\n      private Shared s1;\r\n      private Shared s2;\r\n      public Thread1(Shared s1, Shared s2)\r\n         {\r\n             this.s1 = s1;\r\n             this.s2 = s2;\r\n          }\r\n@Override\r\npublic void run()\r\n   {\r\n      s1.test1(s2);\r\n   }\r\n}\r\nclass Thread2 extends Thread\r\n  {\r\n      private Shared s1;\r\n      private Shared s2;\r\n      public Thread2(Shared s1, Shared s2)\r\n         {\r\n               this.s1 = s1;\r\n               this.s2 = s2;\r\n         }\r\n@Override\r\npublic void run()\r\n   {\r\n       s2.test2(s1);\r\n    }\r\n }\r\npublic class GFG\r\n   {\r\n     public static void main(String[] args)\r\n       {\r\n            Shared s1 = new Shared();\r\n            Shared s2 = new Shared();\r\n            Thread1 t1 = new Thread1(s1, s2);\r\n            t1.start();\r\n            Thread2 t2 = new Thread2(s1, s2);\r\n            t2.start();\r\n            Util.sleep(2000);\r\n        }\r\n   }<\/pre>\n
No one is ever recommended to run this program with online IDE. The alternate technique can be to copy the whole article and then run it on local machines. This can be seen that it runs on indefinite time because of the reason these threads are in a position of deadlock which does no led the codes to be executed.<\/p>\n
Read about Types of Exceptions in Java Programming<\/a><\/strong><\/p>\n
How to Detect Deadlock in Java<\/h3>\n
There is one more method to detect Deadlock in Java, it can be done by running the program in CMD. All we need to do is collect thread dumps and then we have to command to collect, depending upon the operating system. If we are running Java 8 on windows, a command would be jcmd $PID Thread.print.<\/p>\n
5524:<\/p>\n
2017-04-21 09:57:39<\/p>\n
Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode):<\/p>\n
“DestroyJavaVM” #12 prio=5 os_prio=0 tid=0x0000000002690800 nid=0xba8 waiting on condition [0x0000000000000000]
\njava.lang.Thread.State: RUNNABLE<\/p>\n
“Thread-1” #11 prio=5 os_prio=0 tid=0x0000000018bbf800 nid=0x12bc waiting for monitor entry [0x000000001937f000]
\njava.lang.Thread.State: BLOCKED (on object monitor)
\nat Shared.test1(GFG.java:15)
\n– waiting to lock (a Shared)
\nat Shared.test2(GFG.java:29)
\n– locked (a Shared)
\nat Thread2.run(GFG.java:68)<\/p>\n
“Thread-0” #10 prio=5 os_prio=0 tid=0x0000000018bbc000 nid=0x1d8 waiting for monitor entry [0x000000001927f000]
\njava.lang.Thread.State: BLOCKED (on object monitor)
\nat Shared.test2(GFG.java:25)
\n– waiting to lock (a Shared)
\nat Shared.test1(GFG.java:19)
\n– locked (a Shared)
\nat Thread1.run(GFG.java:49)<\/p>\n
“Service Thread” #9 daemon prio=9 os_prio=0 tid=0x000000001737d800 nid=0x1680 runnable [0x0000000000000000]
\njava.lang.Thread.State: RUNNABLE
\n“C1 CompilerThread2” #8 daemon prio=9 os_prio=2 tid=0x000000001732b800 nid=0x17b0 waiting on condition [0x0000000000000000]
\njava.lang.Thread.State: RUNNABLE<\/p>\n
“C2 CompilerThread1” #7 daemon prio=9 os_prio=2 tid=0x0000000017320800 nid=0x7b4 waiting on condition [0x0000000000000000]
\njava.lang.Thread.State: RUNNABLE<\/p>\n
“C2 CompilerThread0” #6 daemon prio=9 os_prio=2 tid=0x000000001731b000 nid=0x21b0 waiting on condition [0x0000000000000000]
\njava.lang.Thread.State: RUNNABLE<\/p>\n
“Attach Listener” #5 daemon prio=5 os_prio=2 tid=0x0000000017319800 nid=0x1294 waiting on condition [0x0000000000000000]
\njava.lang.Thread.State: RUNNABLE<\/p>\n
“Signal Dispatcher” #4 daemon prio=9 os_prio=2 tid=0x0000000017318000 nid=0x1efc runnable [0x0000000000000000]
\njava.lang.Thread.State: RUNNABLE<\/p>\n
“Finalizer” #3 daemon prio=8 os_prio=1 tid=0x0000000002781800 nid=0x5a0 in Object.wait() [0x000000001867f000]
\njava.lang.Thread.State: WAITING (on object monitor)
\nat java.lang.Object.wait(Native Method)
\n– waiting on (a java.lang.ref.ReferenceQueue$Lock)
\nat java.lang.ref.ReferenceQueue.remove(Unknown Source)
\n– locked (a java.lang.ref.ReferenceQueue$Lock)
\nat java.lang.ref.ReferenceQueue.remove(Unknown Source)
\nat java.lang.ref.Finalizer$FinalizerThread.run(Unknown Source)<\/p>\n
“Reference Handler” #2 daemon prio=10 os_prio=2 tid=0x000000000277a800 nid=0x15b4 in Object.wait() [0x000000001857f000]
\njava.lang.Thread.State: WAITING (on object monitor)
\nat java.lang.Object.wait(Native Method)
\n– waiting on (a java.lang.ref.Reference$Lock)
\nat java.lang.Object.wait(Unknown Source)
\nat java.lang.ref.Reference$ReferenceHandler.run(Unknown Source)<\/p>\n
– locked (a java.lang.ref.Reference$Lock)
\n“VM Thread” os_prio=2 tid=0x00000000172e6000 nid=0x1fec runnable<\/p>\n
“GC task thread#0 (ParallelGC)” os_prio=0 tid=0x00000000026a6000 nid=0x21fc runnable<\/p>\n
“GC task thread#1 (ParallelGC)” os_prio=0 tid=0x00000000026a7800 nid=0x2110 runnable<\/p>\n
“GC task thread#2 (ParallelGC)” os_prio=0 tid=0x00000000026a9000 nid=0xc54 runnable<\/p>\n
“GC task thread#3 (ParallelGC)” os_prio=0 tid=0x00000000026ab800 nid=0x704 runnable<\/p>\n
“VM Periodic Task Thread” os_prio=2 tid=0x0000000018ba0800 nid=0x610 waiting on condition<\/p>\n
JNI global references: 6
\nFound one Java-level deadlock:
\n=============================
\n“Thread-1”:
\nwaiting to lock monitor 0x0000000018bc1e88 (object 0x00000000d5d645a0, a Shared),
\nwhich is held by “Thread-0”
\n“Thread-0”:
\nwaiting to lock monitor 0x0000000002780e88 (object 0x00000000d5d645b0, a Shared),
\nwhich is held by “Thread-1”<\/p>\n
Java stack information for the threads listed above:
\n===================================================
\n“Thread-1”:
\nat Shared.test1(GFG.java:15)
\n– waiting to lock (a Shared)
\nat Shared.test2(GFG.java:29)
\n– locked (a Shared)
\nat Thread2.run(GFG.java:68)
\n“Thread-0”:
\nat Shared.test2(GFG.java:25)
\n– waiting to lock (a Shared)
\nat Shared.test1(GFG.java:19)
\n– locked (a Shared)
\nat Thread1.run(GFG.java:49)
\nFound 1 deadlock.
\nThe message displayed in end can happen to appear on your screens too.<\/p>\n
Do you Know 7 Unknown Facts about Null in Java<\/a><\/strong><\/p>\n
How to Reduce Deadlock in Java<\/h3>\n
The occurrence of Deadlock in Java can be avoided by knowing its possibilities. it is really hard to catch one but still possible. The possibility of Java Deadlock cannot be destroyed but it can be reduced.<\/p>\n