EmbeddedActiveMQ is the class you want to use for embedding ActiveMQ
Artemis. The BrokerService is a class from ActiveMQ "Classic". It is used
in the ActiveMQ Artemis code-base only for testing purposes. You won't use
it at all when migrating.
For additional help you'll have to ask more specific q
Good afternoon,
I've been tasked to migrate an existing application's message broker from
ActiveMQ to Artemis. I was wondering if I could get some help
troubleshooting my solution?
We had some initial success replacing our embedded activeMQ broker with a
standalone broker that runs outside the app
I see you're using a metrics plugin. Is this what you're using to determine
the message count? If so, do you have any other way to determine the
message count (e.g. directly from the queue's MBean) in your embedded
environment? I'm asking because I want to eliminate the possibility that
something i
> I’ve been looking for examples on how to use that “options” string in the
ManagementHelper API for listing queues, but I’m coming up empty… can you
point me to a link?
I forgot to address this point...
The "listQueues" method is what the web console uses and what the "artemis
queue stat" CLI co
The ManagementHelper API is there to help you create & structure management
messages which the broker receives and parses in order to invoke methods on
the corresponding JMX MBeans [1]. So in your current code you're
effectively using something like this:
ManagementHelper.putAttribute(request, "
Hi,
Justin, thanks for your advice. I must say, the help given in Apache
communities and on mailinglists are awesome. Cheers everyone! :)
The reasons I believe the count is wrong are: For the period of a few weeks
now, I have performed a handfull of orderly shutdowns and starts of the
embedded br
