Need help testing new Selector implementation on Windows

[Simone Bordet]

Alan et al.,

On Fri, May 14, 2021 at 4:01 PM Alan Bateman <Alan.Bateman at oracle.com> wrote:
>
>
> The implementation of the Selector API on Windows has been replaced in
> JDK 17 b22 with a new more scalable implementation. The old select based
> Selector implementation has been the default since Java 1.4 (2002) so
> replacing it is a significant change. It would be really helpful to get
> more testing of the new implementation before the fork for Rampdown
> Phase One on June 10. If you have an application or workload or tests
> that you know uses the NIO Selector API and can be easily tested on
> Windows then it would be really great if you could spare the time to try
> it out. The JDK 17 Early-Access build page [1] has a download if you
> need it.

We have setup a Jetty 10 + OpenJDK 17+22 on our Jenkins:
https://jenkins.webtide.net/job/nightlies/job/jetty-10.0.x-windows-nightly-jdk17/

There are a few tests failing mostly due to filesystem differences
(deleting files that are in use, etc.) so it's not the cleanest of the
builds, but we'll try to spend some time on it to improve it.
The NIO code is tested quite thoroughly though.
I'm assuming the new implementation is the default and there is
nothing to configure to enable it, right?

-- 
Simone Bordet
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz