-
Type: Improvement
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Usability
-
Labels:None
-
Service Arch
At the moment when the server reaches the connection limit it immediately closes the socket; this leaves the client without any knowledge of the reason for the close. It will seam like a random network error/disconnect.
Instead the server should return a response with an error message of "Connection limit reached! Please look at the server config for : <server:port>".