[jetty-users] Jetty 9.03 - seeing maximum websocket connection limit. wh

["Houtman, Roland" <Roland.Houtman@xxxxxxxxxxxxxxx>]

Hi All,

 

We’re running

  1x Windows 10 inside virtualBox for the server instance 

  3x Windows 10 on a physical machine to run 25 client instances each

 Java 1.8u133 with 2GB ram.

 Jetty 9.03

 

We’re connecting software which opens per instance:

-          two websockets, and

-          some servlets for listing folder content which is invoked regularly. And

-          a servlet for downloading files.

all via HTTPS

When opening about 40 client instances,

Then, setting up the websocket fails more and more. With many tries I got to 52 client software instances running.

The server software is still having 1 GB free heapspace. And no noticeable CPU usage

Which machine the client software runs from(i.e. either single client instance running,or 25 instances running), has no impact on success rate.

 

Does anyone know why this limit is surfacing?

I already read somewhere to increase the QueuedThreadPool. I set it (from default 200) to 750, but there was no noticeable difference.

 

 

Kind regards,

Roland