RockteMQ-AI commented on issue #1344: URL: https://github.com/apache/rocketmq-clients/issues/1344#issuecomment-5412425350
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** Thank you for the detailed report. After reviewing the Python SimpleConsumer implementation (`simple_consumer.py`), the client-side receive mechanism correctly passes `invisible_duration` to the server via `ReceiveMessageRequest`. The redelivery of unacknowledged messages is primarily a server-side responsibility. **Analysis:** - The Python client (v5.1.1) sends `invisible_duration.seconds = 10` correctly in the gRPC request. - After the invisible duration expires without an `ack()`, the server should make the message available for redelivery. - The fact that subsequent `receive()` calls return empty suggests the issue may be on the server side (RocketMQ 5.5.0) or related to how the retry/invisible mechanism handles this specific consumer group configuration. **Recommended investigation:** 1. Check server-side logs for the consumer group to see if the invisible duration expiry triggers redelivery. 2. Verify that the consumer group is configured for retry (not broadcast mode). 3. Try with the Java SimpleConsumer against the same server to isolate whether this is Python-client-specific. 4. Check if `await_duration=15` interacts with the invisible duration timing. This issue is valid and warrants further investigation. --- *Automated evaluation by github-manager* -- 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]
