How does FileLock work?

by

The message about another process just means that some process on your system has the file open. It does not actually check that that process happens to be the same as the one attempting to delete/rename the file. In this case, the same program has the file opened. You have opened it to get the lock. The lock here has little to no value, especially if you are doing this for delete or rename operations.

To do what you want, you would need to lock the directory entry. This is not available in Java and may not be available in Windows. These (delete and insert) operations are atomic. That means that the operating system takes care of locking the directory and other file system structures for you. If another process (or your own) has the file open then these operations will fail. If you are trying to lock the file exclusively (directory entry) and another process (or your own) has the file open, then the lock will fail. There is no difference, but attempting to do the lock just complicates, and in this case, makes the operation impossible (that is, the files are always opened before you attempt to do the operation).

Now writing to the file is a valid lock operation. Lock the file or portion of the file that you want to write to and then it will work. On Windows, this lock mechanism is mandatory so another open/file descriptor will not be able to write to any portion that is under the lock.

EDIT

According to the JavaDoc on FileChannel.lock, it is the same as calling FileChannel.lock(0L, Long.MAXVALUE, false). This is an exclusive lock on a region from the first byte to the last.

Second, according to JavaDoc on FileLock

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.

EDIT

For the testWrite method. The JavaDoc on the commons I/O static method is sparse but says “Writes a String to a file creating the file if it does not exist..” and being as this method takes a File instead of an opened stream, it likely opens the file internally. Probably it is not opening the file with shared access and also opening for append access. This means that the existing open and lock (your open to get the channel from which to get the lock) are blocking that use. To understand even more, you would need to get the source for that method and look at what it is doing.

EDIT

Sorry, I stand corrected. I checked the Windows API and file locking is mandatory on Windows. This is why the write fails. The first open (your new RandomAccessFile) and lock has the file locked. The open to write the string succeeds but the write fails because another open (file descriptor) has the full extent of the file under mandatory exclusive lock – that is, no other file descriptor can write to the file until the lock is released.

Note that locking is associated with the file descriptor NOT process or thread.

More Related Contents:

  1. How to append text to an existing file in Java?
  2. File to byte[] in Java
  3. Scanner vs. BufferedReader
  4. BufferedWriter not writing everything to its output file
  5. How to write a UTF-8 file with Java?
  6. How to write console output to a txt file
  7. Reading a .txt file using Scanner class in Java
  8. List all files from a directory recursively with Java
  9. How do I add a resources folder to my Java project in Eclipse
  10. How do I use Java to read from a file that is actively being written to?
  11. Check line for unprintable characters while reading text file
  12. Is this the best way to rewrite the content of a file in Java?
  13. Check if a file is locked in Java
  14. Reset buffer with BufferedReader in Java?
  15. Is it necessary to close each nested OutputStream and Writer separately?
  16. Write a file in UTF-8 using FileWriter (Java)?
  17. How to tell why a file deletion fails in Java?
  18. I/O concept flush vs sync
  19. java.security.AccessControlException: Access denied (java.io.FilePermission
  20. File truncate operation in Java
  21. Fastest way to sum integers in text file
  22. Write I/O file to shared network drive using credentials
  23. Does BufferedReader.ready() method ensure that readLine() method does not return NULL?
  24. Exception in thread “main” java.io.FileNotFoundException: Error
  25. Java OutOfMemoryError in reading a large text file
  26. Java reading a file different methods
  27. Does collect operation on Stream close the stream and underlying resources?
  28. Using reflection to change static final File.separatorChar for unit testing?
  29. If a synchronized method calls another non-synchronized method, is there a lock on the non-synchronized method
  30. Difference between Files#delete(Path) and File#delete()

Leave a Comment