Hi, This is a known issue. It was solved at JDK18 and was backported to JDK17.0.2. Please see this bug description[1]. You can use JDK18 early access builds[2] to avoid this issue or wait JDK17.0.2 to release. Best Regards, -- Guoxiong [1] https://bugs.openjdk.java.net/browse/JDK-8269113 [2] http://jdk.java.net/18/