maixiaohai opened a new issue #3371: URL: https://github.com/apache/rocketmq/issues/3371
**BUG REPORT** 1. Please describe the issue you observed: - [ ] when we start the pop consumer demo to set MessageRequestMode StackOverflowError exception will be throw ``` Exception in thread "main" org.apache.rocketmq.client.exception.MQClientException: CODE: 1 DESC: java.lang.StackOverflowError, com.google.gson.stream.JsonWriter.beforeName(JsonWriter.java:617) For more information, please visit the url, http://rocketmq.apache.org/docs/faq/ at org.apache.rocketmq.client.impl.MQClientAPIImpl.setMessageRequestMode(MQClientAPIImpl.java:2536) at org.apache.rocketmq.tools.admin.DefaultMQAdminExtImpl.setMessageRequestMode(DefaultMQAdminExtImpl.java:1062) at org.apache.rocketmq.tools.admin.DefaultMQAdminExt.setMessageRequestMode(DefaultMQAdminExt.java:566) at org.apache.rocketmq.example.simple.PopPushConsumer.switchPop(PopPushConsumer.java:46) at org.apache.rocketmq.example.simple.PopPushConsumer.main(PopPushConsumer.java:53) ``` - [ ] when change the consumer group mode to pop and start a consumer, we could not see detail about the pop_retry_topic on the console, only push_retry_topic display.  - [ ] messageRequestMode.json config file should be synced from master to slave in case of a new leader is elected. - [ ] ak & ck message nums are not measurable when writen into system shedule topic 2. Please tell us about your environment: rmq version 4.8 deployed on DLedger mode, backport all the pop consuming patches. 3. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task: - [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 description here, - [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 description here, - ... -- 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]
