dingshuangxi888 opened a new issue, #9862: URL: https://github.com/apache/rocketmq/issues/9862
### Before Creating the Bug Report - [x] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [x] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate. - [x] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Runtime platform environment Messages cannot be consumed by gRPC client when ACL is enabled on both proxy and broker in a storage-compute separation architecture. The broker's pop message interface throws the error 'the broker[%s] pop message is timeout too much'. ### RocketMQ version 5.3.2, 5.3.3, develop ### JDK Version java11 ### Describe the Bug Messages cannot be consumed by gRPC client when ACL 2.0 is enabled on both proxy and broker in a storage-compute separation architecture. The broker's pop message interface throws the error 'the broker[%s] pop message is timeout too much'. ### Steps to Reproduce 1. deploy proxy and broker with ACL 2.0 enabled. 2. use grpc java client to consume message. ### What Did You Expect to See? The grpc client will consume messages when the topic has messages. ### What Did You See Instead? Threse is no message consumed. ### Additional Context _No response_ -- 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]
