YanYunyang opened a new issue, #8363: URL: https://github.com/apache/rocketmq/issues/8363
### 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 4.19.90-23-42.v2101.ky10.x86_64 ### RocketMQ version 5.2.0 ### JDK Version openjdk 1.8 ### Describe the Bug If a consumer client is created through an HTTP request, LatencyFaultToleranceScheduledThread and MQClientFactoryFetchRemoteConfigScheduledThread will change from a regular thread to a daemon thread ### Steps to Reproduce 1.create a daemon thread 2.create and start the consumer client within step1 daemon thread 3.check the status of LatencyFaultToleranceScheduledThread and MQClientFactoryFetchRemoteConfigScheduledThread ### What Did You Expect to See? LatencyFaultToleranceScheduledThread and MQClientFactoryFetchRemoteConfigScheduledThread is daemon thread change to daemon thread ### What Did You See Instead? LatencyFaultToleranceScheduledThread and MQClientFactoryFetchRemoteConfigScheduledThread is daemon thread change to daemon thread ### 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: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
