humkum opened a new issue, #6747:
URL: https://github.com/apache/rocketmq/issues/6747

   ### 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 7
   
   ### RocketMQ version
   
   5.0
   
   ### JDK Version
   
   1.8
   
   ### Describe the Bug
   
   If LMQ name contains file separator, for example "%LMQ%lmq_test/1", which 
would generate a CQ path,like follows:
   
![image](https://github.com/apache/rocketmq/assets/50660789/8fd33b19-7394-485d-b029-a0deee54358a)
   When restart the broker, the broker would stop at check:
   ```
   2023-05-12 16:03:56 WARN main - 
/home/work/hdd1/test/broker/30911/consumequeue/%LMQ%lmq_test/1/0        4096 
length not matched message store config value, please check it manually
   ```
   
   ### Steps to Reproduce
   
   1. Message add UserProperty, and send these messages to broker
   ```
   message.putUserProperty("INNER_MULTI_DISPATCH", "%LMQ%lmq_test/1");
   ```
   2. Wait broker reput cq index.
   3. Restart the broker
   
   ### What Did You Expect to See?
   
   Broker restart success.
   
   ### What Did You See Instead?
   
   Broker start failed because of check CQ file failed.
   
   ```
   2023-03-16 16:03:56 WARN main - 
/home/work/hdd1/test/broker/30911/consumequeue/%LMQ%lmq_test/1/0        4096 
length not matched message store config value, please check it manually
   ```
   
   ### 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]

Reply via email to