Observed on AIX, but possible with any platform that uses the PollingWatchService implementation.
A failing compliance test highlighted issues in the PollingWatchService implementation of the WatchService API. The test was failing due to timeout after 10s. The root of the cause was found to be a delay between when the polling thread was created for a WatchKey, and when it began polling for changes.JDK-8285956 reduced this delay, however some tests continued to fail due to timeout.
A failing compliance test highlighted issues in the PollingWatchService implementation of the WatchService API. The test was failing due to timeout after 10s. The root of the cause was found to be a delay between when the polling thread was created for a WatchKey, and when it began polling for changes.
- duplicates
-
JDK-8298726 (fs) Change PollingWatchService to record last modified time as FileTime rather than milliseconds
-
- Resolved
-
- relates to
-
JDK-8298057 (fs) Remove PollingWatchService.POLLING_INIT_DELAY
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Review
openjdk/jdk/10824