@activemq.apache.org
Subject: Re: [EXTERNAL]:Re: STOMP client receives undefined priority header
when JMSPriority = 4 (default)
[CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe
ctivemq.apache.org
> Subject: Re: [EXTERNAL]:Re: STOMP client receives undefined priority
> header when JMSPriority = 4 (default)
>
> [CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unl
, December 8, 2023 3:42 PM
To: users@activemq.apache.org
Subject: Re: [EXTERNAL]:Re: STOMP client receives undefined priority header
when JMSPriority = 4 (default)
[CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and
: Justin Bertram
> Sent: Thursday, December 7, 2023 11:36 PM
> To: users@activemq.apache.org
> Subject: [EXTERNAL]:Re: STOMP client receives undefined priority header
> when JMSPriority = 4 (default)
>
> [CAUTION: This email originated from outside of the organization. Do not
undefined priority header when
JMSPriority = 4 (default)
[CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.]
I just tested this on the main branch with
JMSPriority is 4?
Thanks again,
Aaron
From: Justin Bertram
Sent: Thursday, December 7, 2023 11:36 PM
To: users@activemq.apache.org
Subject: [EXTERNAL]:Re: STOMP client receives undefined priority header when
JMSPriority = 4 (default)
[CAUTION: This email originated
I just tested this on the main branch with an OpenWire JMS producer and the
STOMP client in our test-suite. The OpenWire JMS producer did not invoke
setJMSPriority and the STOMP client received a message with a header
"priority" with the value "4".
What version of ActiveMQ Artemis are you using? C
Hello,
My STOMP client receives populated priority header values when it consumes
OpenWire JMS messages with valid JMSPriority values except 4. Is this expected
behavior because 4 is the default JMSPriority value? Should the STOMP client
assume the priority is 4 if the priority header is undefi
