JDK-8297275 : WatchService delay with PollingWatchService causes test failures
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.nio
  • Affected Version: 17,19,20
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: aix
  • CPU: generic
  • Submitted: 2022-11-18
  • Updated: 2022-12-27
  • Resolved: 2022-12-27
Related Reports
Duplicate :  
JDK-8298726 - (fs) Change PollingWatchService to record last modified time as FileTime rather than milliseconds
Relates :  
JDK-8298057 - (fs) Remove PollingWatchService.POLLING_INIT_DELAY
Relates :  
JDK-8285956 - (fs) Excessive default poll interval in PollingWatchService
Relates :  
JDK-8298726 - (fs) Change PollingWatchService to record last modified time as FileTime rather than milliseconds
Description
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.
Comments
This issue fixed by JDK-8298726
20-12-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/10824 Date: 2022-10-21 21:43:25 +0000
18-11-2022