@Charith E@Isuru Gunathunga Thus it should be: ThreadLimit should be 1200 * 1.5 = 1800 (1075 licenses + headroom) Max Websocket Clients should be 1800 * 0.75 = 1350 Then ThreadsPerChild should be 1800 - 1350 = 450 Is my reasoning correct or horribly wrong? The websockets are the ones which should be focused on right, because keeping these open will yield the best performance, right? EDIT: I see in the logs that with the configuration above, it lowers the WLMaxWebSocketClients to 337, which is 450 * 0,75. Thus, ThreadsPerChild should be equal to ThreadLimit on Windows (as only 1 process is spawned). When setting ThreadsPerChild = 1800, it now says: [VirtualHost: main] Lowering WLMaxWebSocketClients to 1350. Increase ThreadsPerChild to support more connections Which is what we want, right? @SORSITEL @Charith EpasingheWe are experiencing a similar issue. In our instance the HttpServer1.log files are growing and we are seeing error messages around WebSocket connection Limit Error
Hi @Sajith D Thanks for the reply. ADFS is current configured in a single application mode. When I force MFA via access policy IEE always asks for MFA, but Aurena just seems to log in. We think the issue is causes by a delivery provided by IFS. After reviewing everything and looking at logs and confirming with users it appears to have happened after that was applied. I have a ticket open with support and waiting to hear back from them.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
