GenerousMan opened a new issue, #6706: URL: https://github.com/apache/rocketmq/issues/6706
### 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 CentOS ### RocketMQ version 5.1.0 ### JDK Version _No response_ ### Describe the Bug brokerPermission cannot guarantee that messages will not flow in. If the client has a cache and has not updated it, it will still send a message to the write-forbidden broker. ### Steps to Reproduce #6509 ‘s remaining problem. ### What Did You Expect to See? No message flows in. ### What Did You See Instead? Although the broker is isolated, but clients can still send messages into it. ### 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]
