object entry queue

From: anderson.wolfe@xxxxxxxxx
Date: 30 Nov 2005 00:42:49 -0800

does anybody know if the lock for an object is already owned: if
there's a way to enforce that the jvm always gives the lock to the
thread that's next up in the object's entry queue? i don't want to rely
on the jvm's fair policy, but instead the order in which each thread
was put in the entry queue.

thanks,
andy

.

Prev by Date: Re: Can't find my own exception class via JNI
Next by Date: Re: upcast: I have lost my example
Previous by thread: Java diff viewer Component?
Index(es):
- Date
- Thread

Relevant Pages

Re: object entry queue
... > there's a way to enforce that the jvm always gives the lock to the ... > thread was put in the entry queue. ...
(comp.lang.java.programmer)
Re: meaning of synchronized keyword
... > sleep and that awaken it again are different on different ... > JVM implementations, ... > soon as it finds the lock already taken. ... > writing a non-portable program. ...
(comp.lang.java.programmer)
Re: meaning of synchronized keyword
... >> the opportunity to acquire the lock and execute the method? ... > sleep and that awaken it again are different on different ... > JVM implementations, ... > just spin (making no progress) until the lock is released. ...
(comp.lang.java.programmer)
Re: meaning of synchronized keyword
... > the opportunity to acquire the lock and execute the method? ... JVM implementations, ... thread may spin for a little while and then go to sleep. ... just spin (making no progress) until the lock is released. ...
(comp.lang.java.programmer)
Apparent bug in FileLock
... Reader reader = new FileReader; ... This strongly implies that the IOException is in error: the JVM holding a file lock should not inhibit the same JVM from opening the same file in another manner. ... This situation has arisen from an effort to get an exclusive lock on a file before reading it, then overwriting it after doing some computations. ...
(comp.lang.java.programmer)