Deadlock at page 45: Why `t1` locks `a` and `t2` locks `b`? about learning-examples HOT 1 CLOSED

The reason is that the thread t1 calls send with the Account a from the main program at the first argument, and the Account b at the second place, while the thread t2 does the opposite - it calls the Account b as the first argument, and a as the second. The synchronized statement is called for the two objects a and b from the main program in the opposite order in the two invocations by the thread t1 and t2.

In retrospect, could have been better to call the accounts in the main program x and y, to avoid the confusion.

Hope this helps!

from learning-examples.