With several connections connected, after reconnected, sometimes one of connections can’t receive message however still can send message #1124

Closed
Xiaohongt opened this Issue Dec 12, 2012 · 7 comments

7 participants

@Xiaohongt
SignalR member

Repro on both release and dev branches:
1. You can use the AspNet Sample, Raw/Default.aspx
2. Start 5+ connections with webSockets or foreverFrame transport on IE10
3. Rebuild AspNet Sample
4. Click the “Send to me” button on each connections
5. Sometimes one of connections can’t receive message however still can send message, while other connections receive/send message just fine
6. You can repeat step #3 and #4 to get repro on the issue.

@mahmoudm

I am seeing this as well. It also happens when IIS recycles the app pool.

@bladefist

Experiencing this as well

@davidfowl
SignalR member

This might already be fixed in the next version of 2.0 (the rc). It's likely related to #2207

@davidfowl
SignalR member

@gustavo-armenta can you verify that this was indeed fixed in the upcoming RC

@bladefist

@davidfowl Thanks. I'd be happy to check for you, where can I get the RC?

@davidfowl
SignalR member

@bladefist Sure you can get the nightly package builds from http://myget.org/F/aspnetwebstacknightlyrelease or if you want to use the source, you can build from the release branch. Note that upgrading from 1.x to 2.x is requires manual steps as there's breaking changes. You can read the release notes for beta2 here:

https://github.com/SignalR/SignalR/releases/tag/2.0.0beta2

@davidfowl davidfowl was assigned Aug 12, 2013
@gustavo-armenta

it does not repro anymore, I recycled three times

@davidfowl davidfowl closed this Aug 15, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment