[SERVER-2765] When connection limit is met, return response with errmsg Created: 15/Mar/11 Updated: 06/Dec/22 Resolved: 25/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Fix | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Participants: |
| Description |
|
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>". |
| Comments |
| Comment by Gregory McKeon (Inactive) [ 25/Mar/19 ] |
|
This is expensive, has no obvious implementation, and hasn't gathered enough interest for us to implement at this time. Please file a new SERVER ticket if you still have this issue. |
| Comment by vitaly [ 07/Dec/11 ] |
|
Im really need this kind of server response |
| Comment by Scott Hernandez (Inactive) [ 12/Oct/11 ] |
|
Adding a handshake, or just having the server respond with current status/state, might be a good way to handle this. |