You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been successfully using WebSocketPP for a while now (Thank you), but recently we changed out Client-Server comms from using long lived connections to using shorter lived connections and since then we've been seeing frequent connection failures.
Looking at the error information on the connection failures we were getting an "Underlying Transport Error". Adding further logging to see the transport error details I see that the transport error details are "uninitialized (SSL routines)" (Error 167772436).
If we keep retrying the connection then it eventually succeeds.
Note that a Wireshark capture suggests that nothing is actually happening on the network when these failures occur.
Is this a known problem, or can you think of anything I may be doing wrong?
TY
Ben
P.S. this in on version 0.8.1. I don't see anything in the 0.8.2 release notes that suggests any fixes in this area though, but I'll try it anyway.
The text was updated successfully, but these errors were encountered:
I've been successfully using WebSocketPP for a while now (Thank you), but recently we changed out Client-Server comms from using long lived connections to using shorter lived connections and since then we've been seeing frequent connection failures.
Looking at the error information on the connection failures we were getting an "Underlying Transport Error". Adding further logging to see the transport error details I see that the transport error details are "uninitialized (SSL routines)" (Error 167772436).
If we keep retrying the connection then it eventually succeeds.
Note that a Wireshark capture suggests that nothing is actually happening on the network when these failures occur.
Is this a known problem, or can you think of anything I may be doing wrong?
TY
Ben
P.S. this in on version 0.8.1. I don't see anything in the 0.8.2 release notes that suggests any fixes in this area though, but I'll try it anyway.
The text was updated successfully, but these errors were encountered: