qianye1001 commented on PR #1339:
URL:
https://github.com/apache/rocketmq-clients/pull/1339#issuecomment-5290792074
Follow-up real broker validation was completed with isolated resources
created through metadata gRPC and synchronized by the Controller:
- Logical topic: `Topic_JMX_E2E_20260814_153021`
- Logical consumer group: `Group_JMX_E2E_20260814_153021`
- Physical topic: `T#rmq-cn-medium#00406405`
- Both resources reached `RUNNING` before the client test.
Using the shaded client built from `d426382a` on Alibaba AJDK 21:
1. Started the new consumer group and waited for its queue assignment.
2. Created a fresh producer and verified no send metric existed before
publishing.
3. Called synchronous `producer.send(...)` exactly once.
4. Broker returned message ID `01DE1499736ADC60D50A905E6F00000000`.
5. The isolated consumer received the same message ID and the exact same
body.
6. Before shutdown, JMX reported:
- `rocketmq_send_cost_time_count = 1`
- `rocketmq_send_cost_time_sum = 12 ms`
- `rocketmq_send_cost_time_bucket_le_inf = 1`
- `rocketmq_process_time_count = 1`
7. After closing the producer and consumer, RocketMQ client MBean count
returned to `0`.
The temporary topic, retry/DLQ topics, consumer group, resource mappings,
and metadata rows were removed after the test; read-only verification reported
no matching broker topics and `remainingMetadataRows = 0`.
--
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]
