Hi Rony,
Amazon MQ for ActiveMQ is a managed service and as such it only supports a
limited set of XML configuration attributes. In this case, you are not able to
configure any attributes for the MQTT connector. You can find the full Amazon
MQ XML schemas here:
https://docs.aws.amazon.com/amaz
Hello team,
We are trying to implement mqtt+nio but unfortunately are not able to
configure it.
following are the code what we try to update on configuration xml:
Getting following error:
Error info: The specified XML configuration data is invalid:
cvc-attribute.3: The value 'nio' of attribut
Mark,
Yeah that's kind of where I'm coming from. We've seen that a large number of
queues consumes a lot of broker memory, and we've hit OOM a few times due to
100s to reply-to temporary queues. We've since fixed the reply-to queue count
by having our RPC receivers multiplex a single reply-to q
Hi Justin,
Is there a rule of thumb for the limit of Y?
Just wondering about the realistic upper limit on the number of queues.
Thanks
On Wed, 21 Dec 2022 at 15:21, Justin Bertram wrote:
> Generally speaking I would avoid use-cases involving a JMS queue +
> selectors when possible for the fol
