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
when I run this command : .\mqnamesrv.cmd -c C:\Users\lsZ\namesrv\namesrv.conf, things going unlike what It should be
no matter to use namesrv.conf or namesrv.properties , even those config file contains syntax problem , the program always print like this:
load config properties file OK, C:\Users\lsZ\namesrv\namesrv.conf The Name Server boot success. serializeType=JSON, address 0.0.0.0:9876
use .\mqnamesrv.cmd -p ,printed log always was that , I don't khonw my customized paramerter worked
PS E:\rocketmq-all-5.3.1-bin-release\bin> .\mqnamesrv -p2024-11-13 11:00:36 INFO main - rocketmqHome=E:\rocketmq-all-5.3.1-bin-release2024-11-13 11:00:36 INFO main - kvConfigPath=C:\Users\lsZ\namesrv\kvConfig.json2024-11-13 11:00:36 INFO main - configStorePath=C:\Users\lsZ\namesrv\namesrv.properties2024-11-13 11:00:36 INFO main - productEnvName=center2024-11-13 11:00:36 INFO main - clusterTest=false2024-11-13 11:00:36 INFO main - orderMessageEnable=false2024-11-13 11:00:36 INFO main - returnOrderTopicConfigToBroker=true2024-11-13 11:00:36 INFO main - clientRequestThreadPoolNums=82024-11-13 11:00:36 INFO main - defaultThreadPoolNums=162024-11-13 11:00:36 INFO main - clientRequestThreadPoolQueueCapacity=500002024-11-13 11:00:36 INFO main - defaultThreadPoolQueueCapacity=100002024-11-13 11:00:36 INFO main - scanNotActiveBrokerInterval=50002024-11-13 11:00:36 INFO main - unRegisterBrokerQueueCapacity=30002024-11-13 11:00:36 INFO main - supportActingMaster=false2024-11-13 11:00:36 INFO main - enableAllTopicList=true2024-11-13 11:00:36 INFO main - enableTopicList=true2024-11-13 11:00:36 INFO main - notifyMinBrokerIdChanged=false2024-11-13 11:00:36 INFO main - enableControllerInNamesrv=false2024-11-13 11:00:36 INFO main - needWaitForService=false2024-11-13 11:00:36 INFO main - waitSecondsForService=452024-11-13 11:00:36 INFO main - deleteTopicWithBrokerRegistration=false2024-11-13 11:00:36 INFO main - configBlackList=configBlackList;configStorePath;kvConfigPath2024-11-13 11:00:36 INFO main - bindAddress=0.0.0.02024-11-13 11:00:36 INFO main - listenPort=98762024-11-13 11:00:36 INFO main - serverWorkerThreads=82024-11-13 11:00:36 INFO main - serverCallbackExecutorThreads=02024-11-13 11:00:36 INFO main - serverSelectorThreads=32024-11-13 11:00:36 INFO main - serverOnewaySemaphoreValue=2562024-11-13 11:00:36 INFO main - serverAsyncSemaphoreValue=642024-11-13 11:00:36 INFO main - serverChannelMaxIdleTimeSeconds=1202024-11-13 11:00:36 INFO main - serverSocketSndBufSize=02024-11-13 11:00:36 INFO main - serverSocketRcvBufSize=02024-11-13 11:00:36 INFO main - writeBufferHighWaterMark=02024-11-13 11:00:36 INFO main - writeBufferLowWaterMark=02024-11-13 11:00:36 INFO main - serverSocketBacklog=10242024-11-13 11:00:36 INFO main - serverNettyWorkerGroupEnable=true2024-11-13 11:00:36 INFO main - serverPooledByteBufAllocatorEnable=true2024-11-13 11:00:36 INFO main - enableShutdownGracefully=false2024-11-13 11:00:36 INFO main - shutdownWaitTimeSeconds=302024-11-13 11:00:36 INFO main - useEpollNativeSelector=false2024-11-13 11:00:36 INFO main - clientWorkerThreads=42024-11-13 11:00:36 INFO main - clientCallbackExecutorThreads=142024-11-13 11:00:36 INFO main - clientOnewaySemaphoreValue=655352024-11-13 11:00:36 INFO main - clientAsyncSemaphoreValue=655352024-11-13 11:00:36 INFO main - connectTimeoutMillis=30002024-11-13 11:00:36 INFO main - channelNotActiveInterval=600002024-11-13 11:00:36 INFO main - isScanAvailableNameSrv=true2024-11-13 11:00:36 INFO main - clientChannelMaxIdleTimeSeconds=1202024-11-13 11:00:36 INFO main - clientSocketSndBufSize=02024-11-13 11:00:36 INFO main - clientSocketRcvBufSize=02024-11-13 11:00:36 INFO main - clientPooledByteBufAllocatorEnable=false2024-11-13 11:00:36 INFO main - clientCloseSocketIfTimeout=true2024-11-13 11:00:36 INFO main - useTLS=false2024-11-13 11:00:36 INFO main - socksProxyConfig={}2024-11-13 11:00:36 INFO main - writeBufferHighWaterMark=02024-11-13 11:00:36 INFO main - writeBufferLowWaterMark=02024-11-13 11:00:36 INFO main - disableCallbackExecutor=false2024-11-13 11:00:36 INFO main - disableNettyWorkerGroup=false2024-11-13 11:00:36 INFO main - maxReconnectIntervalTimeSeconds=602024-11-13 11:00:36 INFO main - enableReconnectForGoAway=true2024-11-13 11:00:36 INFO main - enableTransparentRetry=true"Namesrv starts OK"
here is my config file, namesrv.conf almost sames with namesrv.properties, the only difference is = replaced to =
I had swap configStorePath to C:\Users\lsZ\namesrv\namesrv.properties in namesrv.conf , and namesrv.propertiestoo. I had replaced` with \\ or //、 TRUE to true 、FALSE to false
I had deleted empty line
Howevevr, I still can't set orderMessageEnable to true
Steps to Reproduce
see the description and use my config file to run like this
check orderMessageEnable value ,it should be false, just like this issue
What Did You Expect to See?
```console
PS E:\rocketmq-all-5.3.1-bin-release\bin> .\mqnamesrv -p
2024-11-13 11:00:36 INFO main - rocketmqHome=E:\rocketmq-all-5.3.1-bin-release
2024-11-13 11:00:36 INFO main - kvConfigPath= ${your customized location}
2024-11-13 11:00:36 INFO main - configStorePath=${your customized location}
........................
2024-11-13 11:00:36 INFO main - orderMessageEnable=${your customized value}
.......................
"Namesrv starts OK"
```
when you pass config file args: check your config file , exit when your config file with syntax problems and print invalid item
fixed config file don't workd issue
update namesrv config item docs and namesrv -p reuslt, they sholud sames with each other
add description in this repo or rocketme-site , describe how to customize namesrv config, and which parameter we can customized
if we want to send orderly message, do we need to set orderMessageEnable in namesrv ? why nobody mentioned this issue?
What Did You See Instead?
```console
PS E:\rocketmq-all-5.3.1-bin-release\bin> .\mqnamesrv -p
2024-11-13 11:00:36 INFO main - rocketmqHome=E:\rocketmq-all-5.3.1-bin-release
2024-11-13 11:00:36 INFO main - kvConfigPath=C:\Users\lsZ\namesrv\kvConfig.json
2024-11-13 11:00:36 INFO main - configStorePath=C:\Users\lsZ\namesrv\namesrv.properties
........................
2024-11-13 11:00:36 INFO main - orderMessageEnable=false
.......................
"Namesrv starts OK"
```
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
Windows 10 ltsc
RocketMQ version
5.1.3
JDK Version
PS E:\rocketmq-all-5.3.1-bin-release\bin> java --version
openjdk 21.0.1 2023-10-17 LTS
OpenJDK Runtime Environment (build 21.0.1+12-LTS)
OpenJDK 64-Bit Server VM (build 21.0.1+12-LTS, mixed mode, sharing)
Describe the Bug
when I run this command :
.\mqnamesrv.cmd -c C:\Users\lsZ\namesrv\namesrv.conf
, things going unlike what It should benamesrv.conf
ornamesrv.properties
, even those config file contains syntax problem , the program always print like this:.\mqnamesrv.cmd -p
,printed log always was that , I don't khonw my customized paramerter workednamesrv.conf
almost sames withnamesrv.properties
, the only difference is=
replaced to=
Steps to Reproduce
see the description and use my config file to run like this
.\mqnamesrv.cmd -c C:\Users\lsZ\namesrv\namesrv.conf
.\mqnamesrv.cmd -p
orderMessageEnable
value ,it should be false, just like this issueWhat Did You Expect to See?
namesrv -p
reuslt, they sholud sames with each otherrocketme-site
, describe how to customize namesrv config, and which parameter we can customizedorderMessageEnable
in namesrv ? why nobody mentioned this issue?What Did You See Instead?
Additional Context
No response
The text was updated successfully, but these errors were encountered: