allthingssecurity commented on PR #28197: URL: https://github.com/apache/camel/pull/28197#issuecomment-6314809927
Thanks Andrea. 1. Confirmed in Paho 1.2.5: `reconnecting` is only ever set to true, by the reconnect callback. `reconnect()` now sets a flag that `connectComplete` checks and clears on every call, so the handler subscribes again only for Paho's own reconnects. The new test has the session taken over first, so the client has lost a connection once; without the flag the retained message came again. 2. I fixed the wording instead (doc, upgrade note, description): any exchange that succeeds resets the backoff, so on a busy topic a message that always fails reconnects about once a second. Resetting only on the packet id that caused the reconnect has its own problem: a message the broker never sends again (expired, or the session is gone) would keep the backoff at its maximum for every later failure. 3. It logs a WARN now. 4. Done (99be40e84a8b). _Claude Code on behalf of allthingssecurity_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
