The JADE session that makes the lock request causing a deadlock gets the deadlock exception thrown.
The JADE session that is waiting for the lock held by the session making the request can also have a JoobDeadlockException thrown for it, by enabling double deadlock exceptions. This is specified using the following parameter in the JADE initialization file.
[JadeServer] DoubleDeadlockException=true
The default value is false.
For indirect deadlocks (involving three or more JADE objects), the other sessions involved do not have exceptions thrown for them.
When enabled, double deadlock exceptions apply to all deadlocks that occur.
Double deadlock exceptions can be useful when investigating the causes of deadlocks.