wood burning stoves*
The moose likes Programmer Certification (SCJP/OCPJP) and the fly likes syncronization is a problem, is it not? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Certification » Programmer Certification (SCJP/OCPJP)
Reply locked New topic
Author

syncronization is a problem, is it not?

Harvinder Singh
Ranch Hand

Joined: Feb 14, 2003
Posts: 90
Saturday, February 14, 2004
I wrote this code to prove
“In the synchronized block of statements,If instead of a this reference, the expression yielded a reference to another object, the lock associated with that object would be acquired before the thread continued.”
psedocode:
--create a thread in which pass a runnable object of the Funda() class
--run() method calls the synchOther() method which will get the lock on a object of Harry class(har) and goes to sleep for 10 seconds.
--Inside the main() thread now call the name method of the harry() class which should not run since the Thread is holding the lock on har object.

My problem is that in the main method as soon as I call the name() it runs. I hope that I am not making any basic mistakes.Plz make the necessary changes so that the code proves the aforesaid objective.


Hard work beats talent<br />when talent doesn't work hard.<p> - Tim Notke
 
 
subject: syncronization is a problem, is it not?
 
Similar Threads
does invocation of join release the locks on objects the current holds?
Problem with output of The Code
Question about wait() method
syncronization is a problem, is it not?
notifyAll()