Force shut down a client, server execution flow didn't go into IDisconnect.Disconnect () at all #511

Closed
imkow opened this Issue Jul 5, 2012 · 1 comment

Comments

Projects
None yet
3 participants
@imkow

imkow commented Jul 5, 2012

Environment:
a self host server, client is Win8 WinRT app, all 0.5.2, Json.NET 4.5.7, all on Windows 8 Release Preview build 8400.

The same problem when the self host server on Windows Server 2008 R2, client is WinRT app as well.

Repo steps:
client connects server (Hub), does some stuff, and force close the client from Task Manager.

server doesn't detect (server code execution flow doesn't go into IDisconnect.Disconnect()), even after a long time

UPDATE:

RegisterForDisconect never get called, weird

even client called HubConnection.Stop() got server side IDisconnecet.Disconnect() called, no break at RegisterForDisconnect()

@ghost ghost assigned davidfowl Jul 8, 2012

@davidfowl

This comment has been minimized.

Show comment
Hide comment
@davidfowl

davidfowl Jul 8, 2012

Member

This is indeed a bug with the self host implementation and longpolling. We'll fix this for 0.5.3

Member

davidfowl commented Jul 8, 2012

This is indeed a bug with the self host implementation and longpolling. We'll fix this for 0.5.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment