when backplane is not up, in .Net client start webSockets connection and connection become connected, but it should not be connected when backplane is not up.
1). use the asp.net sample as app server
2). in the asp.net sample Startup update to use scale-out but make backplane not up
3). build and start the asp.net sample
4). use Client.Samples for .Net client, build it
5). run the sample exe file, choose webSockets
.Net client webSockets connection become disconnected
connection is connected, here is output from the sample exe:
Disconnected => Connecting
Connecting => Connected
@NTaylorMullen Don't we only raise connect when the init message is received?
@Xiaohongt is this with the latest .NET client as well?
this should be same as the #2219
This was fixed as a result of #2219 as well.