Hi Justin,
Thanks for the response!
Our use case is something like this. Suppose we have a nice RPC client wrapped
around message queues and their services. Some methods take a long time, and
we want to report status along the way, so we’ve arranged for such methods to
return a “task ID”:
S
Hi, Adrija
I too have been working with trying to setup high availability and failover of
active mq artemis on
kubernetes cluster. The Live – Backup Groups section of this doc
https://activemq.apache.org/components/artemis/documentation/latest/ha.html#high-availability-and-failover
describes t
Hi,
I am having an issue with failback to the master broker. I start the master
broker then the slave broker. I see the replication from the master to the
slave happen. I stop the master/active broker and a failover happens to the
slave as expected. When the master is started a failback to i
Hello Timothy,
Thank you very much for this explanation. It’s exactly what I needed. I replied
to Justin’s email before I read it.
Thanks again and have a good weekend,
Aaron
From: Timothy Bish
Sent: Friday, December 8, 2023 3:42 PM
To: users@activemq.apache.or
Given the information provided by Tim on this thread I don't believe this
is a bug but rather the result of a specific design decision.
Justin
On Fri, Dec 8, 2023 at 3:09 PM Steigerwald, Aaron
wrote:
> Hello Justin,
>
> Thank you for checking! Purposely not setting the AMQP priority header if
Hello Justin,
Thank you for checking! Purposely not setting the AMQP priority header if the
value is the JMS default value seems odd to me. I’ll let sleeping dogs lie if
you don’t think it’s a bug.
Thanks again,
Aaron
From: Justin Bertram
Sent: Friday, Decembe
Looking at the code [1] that converts the message from core to AMQP I can
see that it will not set the priority if it's the default value (i.e. 4) so
I would say what you're seeing is expected.
Justin
[1]
https://github.com/apache/activemq-artemis/blob/main/artemis-protocols/artemis-amqp-protoco
The AMQP specification defines that the priority value carried in the
AMQP Header section of the Message has a default value of 4 which means
that an AMQP peer may omit this value on the wire to reduce encoding
size if it chooses to and the receiving peer should interpret that as
carrying the d
Hi Team.
I found
https://stackoverflow.com/questions/76438427/persistent-scheduling-of-activemq-to-disk-leads-to-disk-space-growth
And it makes sense that these would be stuck if something was not acknowledged,
but how do we go about discovering what has not been acknowledged. Normally, I
woul
Hello Justin,
I’m sorry to report that I mistook an old AMQP test client for STOMP. The
problem I reported actually occurs with the RHEA AMQP node.js client code.
Everything else I reported is accurate.
Any idea if the priority should be undefined using an AMQP client when the
message’s JMSPri
> Is it possible to auto-create queues with filter which uses
_AMQ_ORIG_QUEUE instead of _AMQ_ORIG_ADDRESS ?
It is not currently possible to automatically create dead-letter queues
filtered on _AMQ_ORIG_QUEUE.
However, you can effectively get the same behavior by using a
filter/selector on your c
Hi Team,
When we configure address settings for dead-letter queue auto-creation in
ActiveMQ Artemis, all queues on the DLQ address are created with filter based
on _AMQ_ORIG_ADDRESS.
Is it possible to auto-create queues with filter which uses _AMQ_ORIG_QUEUE
instead of _AMQ_ORIG_ADDRESS ?
For e
12 matches
Mail list logo
