[GH-ISSUE #169] Client dies after server disconnection #73

Closed
opened 2026-02-27 15:48:37 +03:00 by kerem · 1 comment
Owner

Originally created by @yankejustin on GitHub (May 23, 2015).
Original GitHub issue: https://github.com/quasar/Quasar/issues/169

Background

- Normal server running - Normal client connected - General normal normalness

Issue

After killing the server, the client (reconnect time: 5000 ms) should automagically try to reconnect. If the server is initialized once again, the client will not connect as it should. This behavior is due to the client, as killing and reinitializing the client will show that the client is connected once again.

In Short

The client does not reconnect (as intended) after the connection to a functional server is broken. The client, instead, will just hang around.

Originally created by @yankejustin on GitHub (May 23, 2015). Original GitHub issue: https://github.com/quasar/Quasar/issues/169 <h1>Background</h1> - Normal server running - Normal client connected - General normal normalness <h1>Issue</h1> After killing the server, the client (reconnect time: 5000 ms) should automagically try to reconnect. If the server is initialized once again, the client will not connect as it should. This behavior is due to the client, as killing and reinitializing the client will show that the client is connected once again. <h1>In Short</h1> The client does not reconnect (as intended) after the connection to a functional server is broken. The client, instead, will just hang around.
kerem 2026-02-27 15:48:37 +03:00
Author
Owner

@yankejustin commented on GitHub (May 23, 2015):

I will investigate these two issues tonight and see why my client is doing this. I will re-open if I still experience issues and will inform you of any irregularities.

<!-- gh-comment-id:104903213 --> @yankejustin commented on GitHub (May 23, 2015): I will investigate these two issues tonight and see why my client is doing this. I will re-open if I still experience issues and will inform you of any irregularities.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Quasar#73
No description provided.