I was actually looking for the management API, thanks for pointing out the
differences. I'll look into jolokia endpoint.
Thai Le
On Sat, Mar 11, 2023, 10:28 Justin Bertram wrote:
> When you say "REST API" do you mean the REST *messaging* API or the
> REST-like *management* API?
>
> We still hav
When you say "REST API" do you mean the REST *messaging* API or the
REST-like *management* API?
We still have the REST-like management API [1] which you can use to get
data from the broker like queue message counts, browse messages, etc. This
API is provided via the Jolokia JMX-HTTP bridge which a
Thank you for the detail explanation. I was looking for a quick way to get
info about queues (number of messages avail, peak some messages...) for
debugging purpose. I guess I just need to make an stand alone app and use
Java client to get those info.
Thai Le
On Fri, Mar 10, 2023, 12:57 Justin Be
This is a case of "working as intended", if the software that uses durable
subscribers will not reconnect messages will be accumulating in internal
queue (this object is not visible as queue, but in webconsole in
"subscribers" tab).
And this messages plus journal files that cannot be dropped becau
Thanks for the reply Matt.
I couldn't find anything in the documentation that indicated that failover:()
to a single load balanced URL was supported.
This made me somewhat nervous about hiding the fact that different brokers
might handle different requests from the client. I imagined a situatio
