Answers to: Too much connect to Ivy Server via IIS

Comment by Hap Em on Flavio Sadeghi's answer

Hap Em — Fri, 28 Aug 2015 08:26:19 -0400

Hello Flavio and namanhem!

Do you have any solution for MaxThreads problem?

Thanks & Regards,

Comment by namanhem on Flavio Sadeghi's answer

namanhem — Tue, 13 May 2014 08:38:58 -0400

Thank Flavio Sadeghi,

I tried update system properties 'WebServer.HTTP.MaxThreads' = 500 'WebServer.AJP.MaxThread' = 500 and update org.atmosphere.useWebSocketAndServlet3 is true. But IIS Server always crashed (but Ivy Server was not crashed) if there are more than 100 Web Socket connections.

Do you have any solution to make sure IIS server will be not crashed if there are more than 100 Web Socket connections.

Thank,

Answer by Flavio Sadeghi

Flavio Sadeghi — Thu, 08 May 2014 16:24:23 -0400

In the Server Administration you could define how many Threads (connections) are allowed by configuring the properties 'WebServer.*.MaxThread', see Chapter 'System Properties' in the Server Guide how to configure.

If you use PrimeFaces Push ensure that for Web Socket connections not IO blocked connections/threads are used. Otherwise each connection use its own Thread. See PrimeFaces Push configuration in the question Can I use PrimePush in Xpert.ivy, especially the init-param 'org.atmosphere.useWebSocketAndServlet3' is required.

Comment by Flavio Sadeghi on namanhem's question

Flavio Sadeghi — Thu, 08 May 2014 15:32:29 -0400

Do you use PrimeFaces Push?