3 ms·
In this case it might be hard to improve. It's a message generated by the client which means that it was expecting something from the server and instead the con
by gtowey 4y ago
In this case it might be hard to improve. It's a message generated by the client which means that it was expecting something from the server and instead the connection was terminated.
It's a sign that something has gone wrong on the server side, but it's impossible for the client to know what that is. Especially because most of the time MySQL connections are each a thread and there may be time between when something server side terminated the thread and when the client tries to talk to the server again. It's better for the server to release all the resources immediately instead of waiting for the client so it can return a more helpful error message.
- wlesieutre 4y ago> the client was expecting something from the server and instead the connection was terminated That’ll do fine
- HelloNurse 4y agoMore classic: the XYZ server "did not respond in a timely fashion": informal (without overly technical concepts like terminating a connection), avoiding possibly wrong or useless details, abstract (implying that the user is a mature person who understands that clients need to communicate with servers) and easily combined with high-level instructions like "check for server problems or network issues".
- tremon 4y agothe XYZ server did not respond in a timely fashion This error message is still potentially wrong and useless though. Potentially wrong: the client is in no position to judge whether the server didn't respond, the server didn't receive the request, or the response got lost along the way. Useless: "timely" isn't succinct enough, what was the developer's expectation of a timely response? 5 seconds? 30 seconds? 5 minutes? "No response received from server XYZ after N seconds" is both more accurate and more informative.
- jodrellblank 4y ago> ""No response received from server XYZ after N seconds" is both more accurate and more informative." Like those news articles which breathlessly report "nobody from the company was immediately available for comment" as if that was as interesting or relevant as a comment would have been. It isn't. Wait a couple of minutes and call them back, then report what they said. Imagine you call Comcast callcenter about your account and the conversation goes: You: "I ordered xyz deal it but I'm still seeing the old price, can you help?" Employee: "Sure, will you hold while I check that on the computer?" You: "Yeah, ok" pause Employee: "No response received from computer after 15 seconds. Click {hangs up} bzzzzzzzzzzzz". You: "that was accurate and informative, thumbs up"
- HelloNurse 4y agoI'd add that it's obviously the client software's job to decide what timeouts (and what behind-the-scenes retries and fallbacks) are appropriate, and when a timely response has arrived or not. The end user doesn't need to know whether, say, waiting 15 seconds is sufficiently generous: there are software engineers for that.
- wlesieutre 4y ago"The connection to the server was lost" is another common phrasing that I like