This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
Which of the following statements about threading are true 1) You can only obtain a mutually exclusive lock on methods in a class that extends Thread or implements runnable 2) You can obtain a mutually exclusive lock on any object 3) A thread can obtain a mutually exclusive lock on a method declared with the keyword synchronized 4) Thread scheduling algorithms are platform dependent Ans : I believe 2 and 4 are right answers. But 3 is also given as right answer. How can a thread obtain a lock on a "method". Isn't is supposed to get lock on object of the method? Any help is greatly appreciated.
Your reasoning is correct. Lock is associated with object not with method. When a thread tries to enter a synchronized method it first tries to accuire the lock of that object ( or class, for static sync. methods). -Paul.
Strictly speaking you cannot obtain a lock on a method but on the objects monitor. However practically what it means is that only one thread can execute that method (or any other synchronized nonstatic methods) at a time. So its a kind of lock Also, obtaining an objects lock has no effect, untill and unless it has some synchronized method or block.So if we consider lock as a situation when other thread can not access that resource, then C is also true.
I belive both Paul and Mohit are correct. To be strictly accurate the lock is on the object not the method. However as it is the method that is affected it is easy (if not correct) to think of the method as getting the lock. I ought to change the wording to refer to the Object lock. Marcus