We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
mac os
5.1.3
java11
Set addressableMessageQueueSet = buildAddressableSet(ctx, mqSet);
addressableMessageQueueSet can be null when Function buildAddressableSet catch exception
Map<String, List> messageQueueSetMap = buildAddressableMapByBrokerName(addressableMessageQueueSet);
in function buildAddressableMapByBrokerName, null will cause NTE
Specially handle the returned null and print the log
no exception
null pointer exception
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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
mac os
RocketMQ version
5.1.3
JDK Version
java11
Describe the Bug
addressableMessageQueueSet can be null when Function buildAddressableSet catch exception
in function buildAddressableMapByBrokerName, null will cause NTE
Steps to Reproduce
Specially handle the returned null and print the log
What Did You Expect to See?
no exception
What Did You See Instead?
null pointer exception
Additional Context
No response
The text was updated successfully, but these errors were encountered: