t; tb...@alumni.duke.edu>;
> 发送时间: 2021年7月14日(星期三) 晚上8:34
> 收件人: "ActiveMQ Users"
> 主题: Re: I have a question use runtimeConfigurationPlugins
>
>
>
> From that stack trace, my best guess is that your broker is not actually
> started. Maybe that's because
The master node starts normally without error log, and the slave node starts
with error log. What's more strange is that each node will expose port 8161. If
the above configuration is removed, the three nodes will start normally. By the
way, what's the impact of setting start to true (start = "f
>From that stack trace, my best guess is that your broker is not actually
started. Maybe that's because of the start="false" snippet you quoted? Or
maybe there's something wrong with the part of your config that you didn't
post? Or maybe your HTTP request is going to a passive broker instead of
the
Hi When i use runtimeConfigurationPlugins on a single broker it works.The
expected effect has been achieved
When I used the same configuration in ActiveMQ + zookeeper, there was an error.
And all three nodes exposed port 8161
This is the activemq.log
WARN || org.eclipse.jetty.servlet.ServletHand
