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
ubuntu 24.04
RocketMQ version
5.3.0
JDK Version
1.8.0
Describe the Bug
rocksDBConfigToJson fail to print subscriptionGroups
Steps to Reproduce
set broker config storeType=defaultRocksDB
create a consumerGroup
run command mqadmin rocksDBConfigToJson -p /tmp/config/ -t subscriptionGroups
What Did You Expect to See?
print subscriptionGroups json success
What Did You See Instead?
print subscriptionGroups json fail
java.lang.NullPointerException
at org.apache.rocketmq.common.config.ConfigRocksDBStorage.iterator(ConfigRocksDBStorage.java:277)
at org.apache.rocketmq.tools.command.metadata.RocksDBConfigToJsonCommand.execute(RocksDBConfigToJsonCommand.java:82)
at org.apache.rocketmq.tools.command.MQAdminStartup.main0(MQAdminStartup.java:190)
at org.apache.rocketmq.tools.command.MQAdminStartup.main(MQAdminStartup.java:139)
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
ubuntu 24.04
RocketMQ version
5.3.0
JDK Version
1.8.0
Describe the Bug
rocksDBConfigToJson fail to print subscriptionGroups
Steps to Reproduce
storeType=defaultRocksDB
mqadmin rocksDBConfigToJson -p /tmp/config/ -t subscriptionGroups
What Did You Expect to See?
print subscriptionGroups json success
What Did You See Instead?
print subscriptionGroups json fail
Additional Context
No response
The text was updated successfully, but these errors were encountered: