Currently there's no way to limit the number of allowed conconurrent
connections to a certain jWebSocket Server or Node.
We want to optionally configure a MAX_CONCURRENT_CONNECTIONS settings in the
jWebSocket.xml and process that by sending an appropriate error token instead
of the welcome message. The connection then will be terminated by the server.
This helps especially to avoid VM crashes due to OutOfMemroy exceptions in case
of machines with small memory.
Original issue reported on code.google.com by fivefeetfurther@gmail.com on 18 Apr 2011 at 3:35
Original issue reported on code.google.com by
fivefeetfurther@gmail.com
on 18 Apr 2011 at 3:35