If you switch the configuration from LevelDB to KahaDB on local storage, do both brokers start successfully? Without a shared filesystem they won't be in a failover pair, but still, do they start and accept/deliver messages? What about if you temporarily set up a database (e.g. SQLite, doesn't have to be something expensive like Oracle) and connect both brokers to it? I'm looking to determine whether the issue is cross-cutting across all data stores or is specific to LevelDB.
I read the documentation[1] and now I see that start=false appears to be required in order to allow the runtime configuration feature to work properly, so disregard my earlier comment about that setting. Tim 1. https://activemq.apache.org/runtime-configuration#:~:text=Note%3A%20the%20start%3D%22false,location%20can%20be%20successfully%20resolved . On Thu, Jul 15, 2021, 2:09 AM ヤ艾枫o.-- <1169114...@qq.com.invalid> wrote: > 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 = "false") > > > ------------------ 原始邮件 ------------------ > 发件人: > "users" > < > tb...@alumni.duke.edu>; > 发送时间: 2021年7月14日(星期三) 晚上8:34 > 收件人: "ActiveMQ Users"<users@activemq.apache.org>; > > 主题: 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 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 active one? > > Tim > > On Wed, Jul 14, 2021, 12:28 AM ヤ艾枫o.-- <1169114...@qq.com.invalid> > wrote: > > > Hi&nbsp; 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.ServletHandler |qtp749115872-17 > > org.apache.jasper.jasperException:An exception occurred processing JSP > > page /xml/queues.jsp at lin2 21 > > 18:<%-- Workaround for https://ops4j1.jira.com/browse/PAXWEB-1070 > --%&gt; > > 19:<%@include file="../WEB-INF/jspf/headertage.jspf" %&gt; > > 20:<queues&gt; > > 21:<c:forEach items="${requestContext.brokerQuery.queses}" > var="row"&gt; > > 22::<queue name="<c:out value="${row.name}"&gt;"&gt; > > 23: > > 24:<stats size="${row.queueSize}"&gt; > > > > > > Stacktrace: > > &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;at > > > org.apache.jasper.servlet.JspServletWrapper.handleJspExcption(JspServletWapper.java:574)[apache-sjp-8.0.33.jar:2.3] > > &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;at > > > org.apache.jasper.servlet.JspServletWraaper.Service(JspServletWrapper.java:476) > > &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; > > > > > > this is my activemq.xml > > <broker .......&nbsp; start="false"&gt; > > <plugins&gt; > > <runtimeConfigurationPlugin checkPeriod="1000"/&gt; > > </plugins&gt;
