Description
When a configured back-end websocket server is not reachable or down then the Knox WebSocket implementation does not close the resources properly which causes the thread count to go up significantly eventually causing OutOfMemory errors.
When a configured back-end websocket server is not reachable or down then the Knox WebSocket implementation does not close the resources properly which causes the thread count to go up significantly eventually causing OutOfMemory errors.