As suggested here: http://mail.openjdk.java.net/pipermail/jmh-dev/2014-August/001354.html
The file lock is the only option to communicate the exclusivity, since users may routinely run JMH from multiple JVMs, e.g. as the result of invoking Java API from JUnit @Test.
The file lock is the only option to communicate the exclusivity, since users may routinely run JMH from multiple JVMs, e.g. as the result of invoking Java API from JUnit @Test.
- relates to
-
CODETOOLS-7901577 JMH file lock works only for the current user, prevents any future runs by other users
-
- Resolved
-
-
-
- Closed
-