I have a cluster of Jetty 7.x servers running with WebSockets currently, but have noticed that after around 1000 users connect through WebSockets it starts to take longer and longer for new session to connect. I've played around with the Jetty thread pool just for kicks to see what happened with no luck. After perusing the internet for a silver bullet fix I came to the conclusion that I should just talk to the community to see if any one else has ran into similar issues. :)
So my question is in general. Is there a setting I need to keep in mind in order to reach a larger number of connections against a single Jetty server or should I be considering another approach to this dilemma (aka bring up additional servers to lighten the load on each box)? Any and all help would be appreciated. Thanks -Pat
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
