We are using SuperWebSocket implementation for a Statistics Call Center application. After starting to simulate some real life scenarios, we went into a point where client connection will always close at the very beginning. More clients that will listen,
more chances to have them disconnected after a few minutes.
Trying to locate the source of this problem, we were using SuperWebSocketWeb sample to push some raw data (just a small string) to the clients at a high rate (ten times per second). We notice that a close connection event occurs in less than a minute
using Google Chrome 14 and Firefox 7 browsers.
Looking in System.Net.Trace.log from SuperWebSocketWeb sample, we noticed this log entries at the point where connection was closed:
Verbose: 0 : Data from Socket#44624228::Send
Verbose: 0 : Socket#44624228::Shutdown(Both#2)
Verbose: 0 : Socket#44624228::Send()
Verbose: 0 : Exiting Socket#44624228::Shutdown()
Error: 0 :  Exception in the Socket#44624228::Send - An established connection was aborted by the software in your host machine
Verbose: 0 :  Socket#44624228::Close()
Verbose: 0 :  Socket#44624228::Dispose()
What do you think it is causing this problem?
I can send you the small changes I've made to SuperWebSocketWeb sample if it helps you to reproduce the problem, but basically we are pushing small raw data to the clients. Even if we are pushing at a slower rate, the same situation will occur at some