This was observed in the Chronicle-Queue Perf build. The maven-exec-plugin is used to run JLBH tests there, they each get their own classloader but live in the same JVM, so the static locks array isn't sufficient to prevent concurrent attempts at locking the lockfiles from a single JVM.
There seems to be an issue where they don't terminate cleanly so they overlap. In any case, handling this exception is more robust.
This was observed in the Chronicle-Queue Perf build. The maven-exec-plugin is used to run JLBH tests there, they each get their own classloader but live in the same JVM, so the static locks array isn't sufficient to prevent concurrent attempts at locking the lockfiles from a single JVM. There seems to be an issue where they don't terminate cleanly so they overlap. In any case, handling this exception is more robust.