You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
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
The text was updated successfully, but these errors were encountered: