|
Java™ Platform Standard Ed. 6 |
|||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object java.nio.channels.FileLock
public abstract class FileLock
A token representing a lock on a region of a file.
A file-lock object is created each time a lock is acquired on a file via
one of the lock
or tryLock
methods of the FileChannel
class.
A file-lock object is initially valid. It remains valid until the lock
is released by invoking the release
method, by closing the
channel that was used to acquire it, or by the termination of the Java
virtual machine, whichever comes first. The validity of a lock may be
tested by invoking its isValid
method.
A file lock is either exclusive or shared. A shared lock prevents other concurrently-running programs from acquiring an overlapping exclusive lock, but does allow them to acquire overlapping shared locks. An exclusive lock prevents other programs from acquiring an overlapping lock of either type. Once it is released, a lock has no further effect on the locks that may be acquired by other programs.
Whether a lock is exclusive or shared may be determined by invoking its
isShared
method. Some platforms do not support shared
locks, in which case a request for a shared lock is automatically converted
into a request for an exclusive lock.
The locks held on a particular file by a single Java virtual machine do
not overlap. The overlaps
method may be used to test
whether a candidate lock range overlaps an existing lock.
A file-lock object records the file channel upon whose file the lock is held, the type and validity of the lock, and the position and size of the locked region. Only the validity of a lock is subject to change over time; all other aspects of a lock's state are immutable.
File locks are held on behalf of the entire Java virtual machine. They are not suitable for controlling access to a file by multiple threads within the same virtual machine.
File-lock objects are safe for use by multiple concurrent threads.
This file-locking API is intended to map directly to the native locking
facility of the underlying operating system. Thus the locks held on a file
should be visible to all programs that have access to the file, regardless
of the language in which those programs are written.
Whether or not a lock actually prevents another program from accessing
the content of the locked region is system-dependent and therefore
unspecified. The native file-locking facilities of some systems are merely
advisory, meaning that programs must cooperatively observe a known
locking protocol in order to guarantee data integrity. On other systems
native file locks are mandatory, meaning that if one program locks a
region of a file then other programs are actually prevented from accessing
that region in a way that would violate the lock. On yet other systems,
whether native file locks are advisory or mandatory is configurable on a
per-file basis. To ensure consistent and correct behavior across platforms,
it is strongly recommended that the locks provided by this API be used as if
they were advisory locks.
On some systems, acquiring a mandatory lock on a region of a file
prevents that region from being On some systems, closing a channel releases all locks held by the Java
virtual machine on the underlying file regardless of whether the locks were
acquired via that channel or via another channel open on the same file. It
is strongly recommended that, within a program, a unique channel be used to
acquire all locks on any given file.
Some network filesystems permit file locking to be used with
memory-mapped files only when the locked regions are page-aligned and a
whole multiple of the underlying hardware's page size. Some network
filesystems do not implement file locks on regions that extend past a
certain position, often 230 or 231. In general, great
care should be taken when locking files that reside on network filesystems.
Platform dependencies
mapped into memory
, and vice versa. Programs that combine
locking and mapping should be prepared for this combination to fail.
Constructor Summary | |
---|---|
protected |
FileLock(FileChannel channel,
long position,
long size,
boolean shared)
Initializes a new instance of this class. |
Method Summary | |
---|---|
FileChannel |
channel()
Returns the file channel upon whose file this lock is held. |
boolean |
isShared()
Tells whether this lock is shared. |
abstract boolean |
isValid()
Tells whether or not this lock is valid. |
boolean |
overlaps(long position,
long size)
Tells whether or not this lock overlaps the given lock range. |
long |
position()
Returns the position within the file of the first byte of the locked region. |
abstract void |
release()
Releases this lock. |
long |
size()
Returns the size of the locked region in bytes. |
String |
toString()
Returns a string describing the range, type, and validity of this lock. |
Methods inherited from class java.lang.Object |
---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait |
Constructor Detail |
---|
protected FileLock(FileChannel channel, long position, long size, boolean shared)
channel
- The file channel upon whose file this lock is heldposition
- The position within the file at which the locked region starts;
must be non-negativesize
- The size of the locked region; must be non-negative, and the sum
position + size must be non-negativeshared
- true if this lock is shared,
false if it is exclusive
IllegalArgumentException
- If the preconditions on the parameters do not holdMethod Detail |
---|
public final FileChannel channel()
public final long position()
A locked region need not be contained within, or even overlap, the actual underlying file, so the value returned by this method may exceed the file's current size.
public final long size()
A locked region need not be contained within, or even overlap, the actual underlying file, so the value returned by this method may exceed the file's current size.
public final boolean isShared()
public final boolean overlaps(long position, long size)
public abstract boolean isValid()
A lock object remains valid until it is released or the associated file channel is closed, whichever comes first.
public abstract void release() throws IOException
If this lock object is valid then invoking this method releases the lock and renders the object invalid. If this lock object is invalid then invoking this method has no effect.
ClosedChannelException
- If the channel that was used to acquire this lock
is no longer open
IOException
- If an I/O error occurspublic final String toString()
toString
in class Object
|
Java™ Platform Standard Ed. 6 |
|||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
Copyright © 1993, 2015, Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.