OverlappingFileLockException

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

When creating a repository a 500 error is returned.

The following can be seen in the atlassian-bitbucket.log:

1 2 3 4 5 6 2017-02-06 18:42:16,963 ERROR [http-apr-7990-exec-1] user_name @9KXPVZx1122x313x0 o2utpk 172.17.0.1 "POST /projects/project_slug/repos HTTP/1.1" c.a.s.i.w.HandlerExceptionResolverImpl null java.nio.channels.OverlappingFileLockException: null at sun.nio.ch.SharedFileLockTable.checkList(FileLockTable.java:255) ~[na:1.8.0_111] at sun.nio.ch.SharedFileLockTable.add(FileLockTable.java:152) ~[na:1.8.0_111] at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:1108) ~[na:1.8.0_111] at java.nio.channels.FileChannel.tryLock(FileChannel.java:1155) ~[na:1.8.0_111]

Environment

Bitbucket Server has been installed in a Docker container and Dropbox is used as the volume where $BITBUCKET_HOME is located.

Cause

Using Dropbox as a host volume causes issues due to the way permissions are handled.

Resolution

Do not use Dropbox as the host volume. A local or NFS volume should be used instead.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.