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.
Commit 0f207409c02fff54e3fb3a5a1c0b3865ef91e7db in knox's branch refs/heads/master from moresandeep
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=0f20740 ]
KNOX-936- On websocket error properly close all the sessions and containers.