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
Hey there. Following up on the other issue I reported recently, I finally managed to get some additional logs:
I really do not know how to reproduce this issue, but I think this is key to figuring it out. It appears that when the client successfully reconnects here and then goes on to restore subscriptions here the connection may drop again before all subscriptions are re-established when the network isn't stable (or the process is under huge pressure) and that code isn't handling a connection loss event properly which trigger the removal that I don't think is correct behavior. Generally a very specific class of errors should trigger removal of all subscriptions and when the client isn't connected, this should juts eject out of that code and retry the whole reconnection again. Thoughts?
In case it helps, here's our configuration of AdsClient:
Hey there. Following up on the other issue I reported recently, I finally managed to get some additional logs:
I really do not know how to reproduce this issue, but I think this is key to figuring it out. It appears that when the client successfully reconnects here and then goes on to restore subscriptions here the connection may drop again before all subscriptions are re-established when the network isn't stable (or the process is under huge pressure) and that code isn't handling a connection loss event properly which trigger the removal that I don't think is correct behavior. Generally a very specific class of errors should trigger removal of all subscriptions and when the client isn't connected, this should juts eject out of that code and retry the whole reconnection again. Thoughts?
In case it helps, here's our configuration of AdsClient:
The text was updated successfully, but these errors were encountered: