We are seeing the exception around 300 -500 a day
What does this mean , is there any way to solve this
We are seeing the exception around 300 -500 a day
What does this mean , is there any way to solve this
These errors likely indicate that a socket connection was closed while data was being written to it. While this is an exceptional occurrence, it should not affect the functionality of the community because it likely indicates a browser/window/tab close. A user was not presented an error and the next page load (or automatic socket reconnection) will restore the connection.
These errors likely indicate that a socket connection was closed while data was being written to it. While this is an exceptional occurrence, it should not affect the functionality of the community because it likely indicates a browser/window/tab close. A user was not presented an error and the next page load (or automatic socket reconnection) will restore the connection.
"Exceptional occurrence" as in rare or as in raises an exception in code?
Actually, both. The messages sent over socket connections are generally very short so the opportunity to close the connections while sending is short-lived making it rare. It also does raise an exception in code that Community is dependent on (SignalR).