Thank you for the information and details surrounding it. If it is required with Spring 6.2.x why did it give me errors on start-up and why did it work when I remove it.
Jason ________________________________ From: Jean-Baptiste Onofré <[email protected]> Sent: Tuesday, April 28, 2026 10:29 AM To: [email protected] <[email protected]> Subject: Re: Apache ActiveMQ Classic 6.2.5 jetty.xml Question CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. This is the first time you received an email from this sender ([email protected]). Exercise caution when clicking links, opening attachments or taking further action, before validating its authenticity. Hi Jason The purpose of this change is to "couple" Jetty server start with broker start (to avoid to start the Jetty server before the broker and have an inconsistent state). It's allow also to have the webconsole started on a slave broker with redirection to This change is required also by Spring 6.2.x. as the lenient locking mechanism changed. Here's the corresponding PR: https://github.com/apache/activemq/pull/1931 and the details of this change: https://github.com/apache/activemq/issues/1907 I agree that I should have included a clearer "change" in the Release Notes. I gonna update it right now. Thanks! Regards JB On Mon, Apr 27, 2026 at 7:48 PM Jason Jackson <[email protected]> wrote: > I recently began testing the latest release of ActiveMQ Classic 6.2.5. > > The broker was failing to start; I noticed the issue was within the > jetty.xml file. > > Looking through the log files, I was able to determine the failure was due > to the following entry. > > <bean id="invokeStart" > class="org.springframework.beans.factory.config.MethodInvokingFactoryBean" > depends-on="broker, configureJetty, invokeConnectors"> > > When I compared the new and old jetty.xml file I noticed the broker entry > is new. > > I removed the broker entry and the broker started fine. I am using the > same settings for 6.2.5 that I used in 6.2.4. > > What is the broker entry/reference for and did I miss anything in the > release notes? > > > Jason >
