|Re: [jetty-users] Port usage by Jetty due to Selector.open()|
Hi, On Tue, May 16, 2023 at 12:55 AM Stefan Feenstra <stefan.feenstra@xxxxxxx> wrote: > > Hi, > > It appears that when I run a Jetty webserver with a servlet that uses JettyHttpClient and Websockets that various ports are being opened. > I have traced this back to the usage of Selectors, Selector.open() seems to use the JDK WindowsSelectorImpl class which then opens a Pipe which in turn uses the port numbers. > > Unfortunately, this is resulting in problems with some strict firewalls that don’t want any ports to be opened except whitelisted port numbers. Is there any way to get Jetty to not open these ports to communicate internally? This is an internal Windows implementation in the JDK on which we have no control over. See: https://forums.oracle.com/ords/apexds/post/selector-open-uses-two-tcp-ports-on-windows-3123 -- Simone Bordet ---- http://cometd.org http://webtide.com Developer advice, training, services and support from the Jetty & CometD experts.
Back to the top