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
If you get an AMQPConnectionException with the message "Library error: a SSL error occurred" or "a socket error occurred", is it safe to retry or in theory is it possible to get this exception after a message is successfully published on the server but before the response was received by the client?
I think if the timing is just right and you have retries implemented, then you could end up double publishing the message in failure scenarios.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
If you get an AMQPConnectionException with the message "Library error: a SSL error occurred" or "a socket error occurred", is it safe to retry or in theory is it possible to get this exception after a message is successfully published on the server but before the response was received by the client?
I think if the timing is just right and you have retries implemented, then you could end up double publishing the message in failure scenarios.
Related to this change in Symfony symfony/symfony#54167 (comment)
Beta Was this translation helpful? Give feedback.
All reactions