• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Jj Roberts
  • Tim Holloway
  • Piet Souris
Bartenders:
  • Himai Minh
  • Carey Brown
  • salvin francis

monitor and object lock

 
Ranch Hand
Posts: 158
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
wats aquring a monitor on object ,
and wats object locking .

can any one explain me confused.
 
Wanderer
Posts: 18671
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"Acquiring a monitor", "locking an object", "acquiring a lock on an object", "synchronizing on an object" - those all mean the same thing, essentially. I'm not going to explain in detail, as I assume you have some book that you're learnign from. (If not, you can use Thinking In Java - chapter 14 talks about synchronization. If you have more specific questions about locking, you can post them here.
 
Ranch Hand
Posts: 146
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
All objects in java have a lock. Another term for lock is monitor. All classes have lock too. so you have object level lock and class level lock.
When compiler encounters any code surrounded by 'synchronized' keyword, It means that it make sure that a thread would acquirer lock/monitor first before actually entering to "synchronized block".

This way threads synchronize with each other on shared data.

For more details: Pls refer Khalid Mughal's book on java.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic