Messages sent to the client by the hub are replicated for every time I stopped / started the connection.
If I follow this sequence: $ .connection.hub.stop () $ .connection.hub.start () {...}
and send a message from the server hub to the client, the message will be received once. If I repeat the above sequence, I get the same message twice, even if the calls to the Clients.Client server hub (Context.ConnectionId) .acceptMsg (MSG); only 1 time. acceptMsg is called twice to the client for the same message with connectionId. I get the same results using Clients.All.acceptMsg (msg)
For each subsequent stop / start, the message is further duplicated; three messages for the third time, four messages for the fourth, etc.
I tried to separate the stop call and start for a couple of minutes, but that didn't make any difference.
Other details: Javascript client, SignalR v2.0.1, Chrome version 31.0.1650.63, ASP.Net 4.5. SignalR uses lengthy polling in my test, and I allow negotiations by default. In the SignalR track "SignalR: Aborted xhr request". observed after stopping, before starting.
Any idea what causes the replication of my posts in this scenario?
source share