| Author |
Is it deadlock?
|
abalfazl hossein
Ranch Hand
Joined: Sep 06, 2007
Posts: 602
|
|
Hello In the above code, the synchronized method a(), when executed, obtains a lock on it's own object. It then calls synchronized method b() which also needs to acquire a lock on it's own object. If Java did not allow a thread to reacquire it's own lock method b() would be unable to proceed until method a() completed and released the lock; and method a() would be unable to complete until method b() completed. Result: deadlock Is it deadlock? [ October 30, 2007: Message edited by: Jim Yingst ]
|
 |
Jim Yingst
Wanderer
Sheriff
Joined: Jan 30, 2000
Posts: 18670
|
|
Did you try running it? If the methods complete and the JVM exits, that's a clue that it's not deadlock. Java synchronization is reentrant. Deadlock will only occur when you're talking about locks on two or more different monitor objects. I edited your post to move the discussion out of the code block - the lines were too long, and messed up the formatting of the page. (Inside code blocks, line breaks will not be inserted automatically.)
|
"I'm not back." - Bill Harding, Twister
|
 |
 |
|
|
subject: Is it deadlock?
|
|
|