I would recommend instead modifying your server.xml to use Tomcat's
non-blocking ("NIO") connector. The standard blocking connector typically
configured in server.xml works great for HTTP connections but quickly runs
out of threads when long-running WebSocket connections come into play. The
non-blocking connector does not run into the same limitation with respect
to WebSocket.

Michael Jumper
CEO, Lead Developer
Glyptodon Inc <https://enterprise.glyptodon.com/>.


On Tue, Nov 17, 2020 at 11:12 PM kstefan <[email protected]> wrote:

> Just for the record - I've found what was my problem.
>
> I was using Zer0Coolx installation script for Centos 7 and it by default
> sets  maxThreads="150" in tomcat server.xml configuration file. I've raised
> this value and my problem has gone.
>
>
>
>
>
> --
> Sent from:
> http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to