java.lang.Object | |
↳ | java.nio.channels.FileLock |
A FileLock
represents a locked region of a file.
Locks have certain properties that enable collaborating processes to avoid
the lost update problem or reading inconsistent data. Logically, a file lock
can be exclusive or shared. Multiple processes can hold
shared locks on the same region of a file, but only a single process can hold
an exclusive lock on a given region of a file and no other process can
simultaneously hold a shared lock overlapping the exclusive lock. An
application can determine whether a FileLock
is shared or exclusive
via the isShared()
method.
Locks held by a particular process cannot overlap one another. Applications
can determine whether a proposed lock will overlap by using the overlaps(long, long)
) method. Locks held in other processes may overlap
locks held in this process. Locks are shared amongst all threads in the
acquiring process, and are therefore unsuitable for intra-process
synchronization.
Once a lock is acquired, it is immutable in all its state except isValid()
. The lock will initially be valid, but may be rendered invalid by
explicit removal of the lock, using release()
, or implicitly by
closing the channel or exiting the process (terminating the virtual machine).
Locks are intended to be true platform operating system file locks, and therefore locks held by the virtual machine process will be visible to other operating system processes.
The characteristics of the underlying operating system locks will show through in the Java implementation. For example, some platforms' locks are 'mandatory' -- meaning the operating system enforces the locks on processes that attempt to access locked regions of files; whereas other platforms' locks are only 'advisory' -- meaning that processes are required to collaborate to ensure locks are acquired and there is a potential for processes to not play well. To be on the safe side, it is best to assume that the platform is adopting advisory locks and always acquire shared locks when reading a region of a file.
On some platforms, the presence of a lock will prevent the file from being memory-mapped. On some platforms, closing a channel on a given file handle will release all the locks held on that file -- even if there are other channels open on the same file; their locks will also be released. The safe option here is to ensure that you only acquire locks on a single channel for a particular file and that becomes the synchronization point.
Further care should be exercised when locking files maintained on network file systems, since they often have further limitations.
Protected Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Constructs a new file lock instance for a given channel.
|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Returns the lock's FileChannel.
| |||||||||||
Indicates if the file lock is shared with other processes or if it is
exclusive.
| |||||||||||
Indicates whether this lock is a valid file lock.
| |||||||||||
Indicates if the receiver's lock region overlaps the region described
in the parameter list.
| |||||||||||
Returns the lock's starting position in the file.
| |||||||||||
Releases this particular lock on the file.
| |||||||||||
Returns the length of the file lock in bytes.
| |||||||||||
Returns a string that shows the details of the lock suitable for display
to an end user.
|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class java.lang.Object
|
Constructs a new file lock instance for a given channel. The constructor enforces the starting position, length and sharing mode of the lock.
channel | the underlying file channel that holds the lock. |
---|---|
position | the starting point for the lock. |
size | the length of the lock in number of bytes. |
shared | the lock's sharing mode of lock; true is shared,
false is exclusive. |
Returns the lock's FileChannel.
Indicates if the file lock is shared with other processes or if it is exclusive.
true
if the lock is a shared lock, false
if it is
exclusive.Indicates whether this lock is a valid file lock. The lock is valid unless the underlying channel has been closed or it has been explicitly released.
true
if the lock is valid, false
otherwise.Indicates if the receiver's lock region overlaps the region described in the parameter list.
start | the starting position for the comparative lock. |
---|---|
length | the length of the comparative lock. |
true
if there is an overlap, false
otherwise.Returns the lock's starting position in the file.
Releases this particular lock on the file. If the lock is invalid then this method has no effect. Once released, the lock becomes invalid.
ClosedChannelException | if the channel is already closed when an attempt to release the lock is made. |
---|---|
IOException | if another I/O error occurs. |
Returns the length of the file lock in bytes.
Returns a string that shows the details of the lock suitable for display to an end user.