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 found this your example on how to implement a beautiful reconnect logic. I assume that pending channel that we use for retry failed delivery on the next session should be moved out of sessions for loop f.e. to the line 93. I made a test simulating error on publishing and the message was not republished to the new session with the current version of an example. When I moved pending channel out of the sessions loop it worked fine. I can provide some code examples if it is required.
Reproduction steps
simulate 1 time error on publishing and call
pending <- body
pub.Close()
break Publish
send a message and check if it was republished and correctly processed with the subscriber
Expected behavior
message republished to the new reconnected session
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
I found this your example on how to implement a beautiful reconnect logic. I assume that pending channel that we use for retry failed delivery on the next session should be moved out of sessions for loop f.e. to the line 93. I made a test simulating error on publishing and the message was not republished to the new session with the current version of an example. When I moved pending channel out of the sessions loop it worked fine. I can provide some code examples if it is required.
Reproduction steps
pending <- body
pub.Close()
break Publish
Expected behavior
message republished to the new reconnected session
Additional context
No response
The text was updated successfully, but these errors were encountered: