Modifier and Type | Field and Description |
---|---|
protected int |
counter_
number of times thread has acquired the lock
|
protected boolean |
debug |
protected Thread |
holder_
The thread holding the lock
|
ONE_CENTURY, ONE_DAY, ONE_HOUR, ONE_MINUTE, ONE_SECOND, ONE_WEEK, ONE_YEAR
Constructor and Description |
---|
ReentrantMutex() |
ReentrantMutex(boolean debug) |
Modifier and Type | Method and Description |
---|---|
void |
acquire()
Wait (possibly forever) until successful passage.
|
boolean |
attempt(long msecs)
Wait at most msecs to pass; report whether passed.
|
void |
release()
Potentially enable others to pass.
|
protected Thread holder_
protected int counter_
protected boolean debug
public ReentrantMutex()
public ReentrantMutex(boolean debug)
public void acquire() throws InterruptedException
Sync
acquire
in interface Sync
InterruptedException
public void release()
Sync
Because release does not raise exceptions, it can be used in `finally' clauses without requiring extra embedded try/catch blocks. But keep in mind that as with any java method, implementations may still throw unchecked exceptions such as Error or NullPointerException when faced with uncontinuable errors. However, these should normally only be caught by higher-level error handlers.
public boolean attempt(long msecs) throws InterruptedException
Sync
The method has best-effort semantics: The msecs bound cannot be guaranteed to be a precise upper bound on wait time in Java. Implementations generally can only attempt to return as soon as possible after the specified bound. Also, timers in Java do not stop during garbage collection, so timeouts can occur just because a GC intervened. So, msecs arguments should be used in a coarse-grained manner. Further, implementations cannot always guarantee that this method will return at all without blocking indefinitely when used in unintended ways. For example, deadlocks may be encountered when called in an unintended context.
attempt
in interface Sync
msecs
- the number of milleseconds to wait.
An argument less than or equal to zero means not to wait at all.
However, this may still require
access to a synchronization lock, which can impose unbounded
delay if there is a lot of contention among threads.InterruptedException
Copyright © 2021 JBoss by Red Hat. All rights reserved.