yuz10 opened a new issue, #8681: URL: https://github.com/apache/rocketmq/issues/8681
### 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 Ubuntu 24.4.0 ### RocketMQ version 5.3.0-SNAPSHOT ### JDK Version 1.8.0 ### Describe the Bug In early versions, if accessChannel is "LOCAL", message trace is sent to "RMQ_SYS_TRACE_TOPIC", or defined by user, else if accessChannel is "LOCAL", message trace is sent to topic "rmq_sys_TRACE_DATA_{region}". Now, message trace is sent to topic "rmq_sys_TRACE_DATA_{region}", regardless of accessChannel. ### Steps to Reproduce start producer or consumer with trace enabled. ### What Did You Expect to See? if accessChannel is "LOCAL", message trace is sent to "RMQ_SYS_TRACE_TOPIC", or defined by user, else if accessChannel is "LOCAL", message trace is sent to topic "rmq_sys_TRACE_DATA_{region}". ### What Did You See Instead? message trace is sent to topic "rmq_sys_TRACE_DATA_{region}", regardless of accessChannel. ### 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]
