the partial list of the Management API MBeans is in the documentation[1],
i.e. to list the addresses you can use the getQueueNames method of
ActiveMQServerControl
curl -v -H "Origin: http://localhost"; -u admin:admin
http://localhost:8161/console/jolokia/read/org.apache.activemq.artemis:broker=\
"
Hi Ben,
by default, a new ActiveMQ Artemis instance doesn't include a line
for jolokia war (), I guess it was add manually.
The ActiveMQ Artemis Console war already includes an embedded jolokia agent
that is available as a subpath of the console endpoint, i.e.
https://[host]:8443/console/jolokia
.
I am pleased to announce the release of Apache Apache.NMS.AMQP 2.1.0
Downloads are now available at:
https://activemq.apache.org/components/nms/providers/amqp/downloads/nms-amqp-02-01-00-release
Or via NuGet:
https://www.nuget.org/packages/Apache.NMS.AMQP/2.1.0
Many thanks to the contributors t
Hi again,
The example of the curl command to jolokia endpoint is fetching the Version
attribute of the org.apache.activemq.artemis:broker mbean, is there other
mbean like address, queue, message that i can query?
On Sat, 11 Mar 2023 at 11:28, Thai Le wrote:
> I was actually looking for the manag
I have a few servers (Ubuntu VMs) running Artemis 2.14. When I check the
version of Jolokia through the console it shows Jolokia 1.6.2
However, I can also see that Jolokia is available through the same port as
the Artemis console -- https://[host]:8443/jolokia -- and that it's version
1.3.5 (Which
Hi folks,
I am looking into this issue: https://issues.apache.org/jira/browse/AMQ-8611
I believe that jira is a casualty of
https://issues.apache.org/jira/browse/AMQ-8029
In AMQ-8029 I see this comment: "I introduced a dependency on commons-io's
BoundedInputStream for this, with a default (con
