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

   ### 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
   
   All
   
   ### RocketMQ version
   
   develop
   
   ### JDK Version
   
   All
   
   ### Describe the Bug
   
   In `rmq.broker.logback.xml`, the filter appender is mistakenly named 
`RocketmqRebalanceLockSiftingAppender`, causing filter and rebalance lock logs 
to be routed incorrectly.
   
   ### Steps to Reproduce
   
   Start a broker using `rmq.broker.logback.xml`. Start a clustering 
`DefaultMQPushConsumer` with `MessageListenerOrderly` and a new consumer group, 
then check the queue lock logs.
   
   ### What Did You Expect to See?
   
   Rebalance lock logs in `lock.log`.
   
   ### What Did You See Instead?
   
   Rebalance lock logs appear in `filter.log`.
   
   ### 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