It was disabled as part of this PR: https://github.com/apache/activemq/pull/2014
You should be able to re-enable it in the web.xml file, there is a comment about it. But the warning applies, it's very much "use at your own risk." That servlet has numerous security vulnerabilities, so much so that we just deprecated it for removal because fixing it would break the entire API anyways. If you use it you should not be exposing the service, or at the very least be using mutual TLS. Chris On Tue, Jul 21, 2026 at 2:59 PM Jason Jackson <[email protected]> wrote: > > I have an old legacy application that uses the API Post to place messages on > a queue. > > After upgrading to the latest release of ActiveMQ 6.2.7, this feature is now > disabled. > > I am working diligently to migrate the application to a new service but until > that is completed, I need the ability to post a message to a queue using an > API call. > > I have gone through and compared numerous files in the latest release and the > older releases and can not determine what needs to be uncommented or added > back in order to allow for an API Post. > > The API post in previous releases allowed for a command like the following to > work: > > Https://amq_broker.host:8162/api/message/API_QUEUE?type=queue > > With the latest release this command does not work and the following is > returned. > > HTTP EROOR 503 Service unavailable > > Any assistance or suggestions are appreciated. > > Thank you. > > > Jason --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
