Aias00 opened a new issue, #10933: URL: https://github.com/apache/rocketmq/issues/10933
## Problem When a consumer channel goes offline, `DefaultReceiptHandleManager.clearGroup` asynchronously renews each receipt handle with `CLEAR_GROUP`. The cleanup callback currently returns `CompletableFuture.completedFuture(null)` immediately instead of the `RenewEvent` future. As a result, `ReceiptHandleGroup` removes the handle before the renewal outcome is known. If the renewal request fails, the handle is no longer retained or retried by the renewal scheduler. ## Expected behavior A receipt handle should be removed only after its `CLEAR_GROUP` renewal succeeds. On failure it should remain in the group so subsequent cleanup scheduling can retry it. ## Proposed fix Return the `RenewEvent` future from the `ReceiptHandleGroup` callback, mapping a successful result to `null` (remove) while preserving exceptional completion (retain). Add a regression test covering a failed offline cleanup renewal. ## Scope Proxy POP receipt-handle lifecycle; no protocol/API changes. -- 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]
