You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by "Hoyt, Michael" <mi...@accenture.com.INVALID> on 2023/10/11 17:27:13 UTC
Queue depth determination change in amq 5.18.2?
Good afternoon. I write on behalf of a client that is using the AMQ REST API to try and determine when an external application has processed all the messages in a particular queue. Previously, in AMQ 5.18.1, this method would return a "204 No Content" response but in 5.18.2 they are instead receiving "500 Server Error". Is this an intended change between the two versions?
Client has provided the additional details below in the hopes that it provides some clarity:
To check if Cycle is complete, we continue to poll the Response queue by making HTTP GET call using a URL like this - https://xxxxxxxx/activemq/api/message/xxxxxQUEUE?timeout=10&type=queue&oneShot=true
We pass in the JMSCorrelationID in a header named "selector" with value "JMSCorrelationID='3cbcaa8a-6f38-457a-aa5d-cb260cab0ace'"
Thanks in advance for any assistance at all whatsoever,
Michael Hoyt
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security, AI-powered support capabilities, and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________
www.accenture.com
RE: [External] Re: Queue depth determination change in amq 5.18.2?
Posted by "Hoyt, Michael" <mi...@accenture.com.INVALID>.
Thank you both. I have created the JIRA as requested.
https://issues.apache.org/jira/browse/AMQ-9330
Regards,
-M
-----Original Message-----
From: Jean-Baptiste Onofré <jb...@nanthrax.net>
Sent: Thursday, October 12, 2023 12:49 PM
To: michael.hoyt@accenture.com.invalid
Cc: users@activemq.apache.org; Mellen, Janet L. <ja...@accenture.com>
Subject: [External] Re: Queue depth determination change in amq 5.18.2?
CAUTION: External email. Be cautious with links and attachments.
Can you please create a Jira ? I suspect it could be related to Jetty update. I will check.
Regards
JB
On Wed, Oct 11, 2023 at 7:27 PM Hoyt, Michael <mi...@accenture.com.invalid> wrote:
>
> Good afternoon. I write on behalf of a client that is using the AMQ REST API to try and determine when an external application has processed all the messages in a particular queue. Previously, in AMQ 5.18.1, this method would return a "204 No Content" response but in 5.18.2 they are instead receiving "500 Server Error". Is this an intended change between the two versions?
>
> Client has provided the additional details below in the hopes that it provides some clarity:
> To check if Cycle is complete, we continue to poll the Response queue
> by making HTTP GET call using a URL like this -
> https://urldefense.com/v3/__https://xxxxxxxx/activemq/api/message/xxxx
> xQUEUE?timeout=10&type=queue&oneShot=true__;!!OrxsNty6D4my!_saPxBaOJnD
> TzqRwGgps1DrWgkJLafp1hyqmJDkRXogJ62n9LS5-_3zYXhUrWmj2j2ZySFkAzmMenwBa$
> We pass in the JMSCorrelationID in a header named "selector" with value "JMSCorrelationID='3cbcaa8a-6f38-457a-aa5d-cb260cab0ace'"
>
> Thanks in advance for any assistance at all whatsoever, Michael Hoyt
>
>
> ________________________________
>
> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security, AI-powered support capabilities, and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
> ______________________________________________________________________________________
>
> http://www.accenture.com
Re: Queue depth determination change in amq 5.18.2?
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Can you please create a Jira ? I suspect it could be related to Jetty
update. I will check.
Regards
JB
On Wed, Oct 11, 2023 at 7:27 PM Hoyt, Michael
<mi...@accenture.com.invalid> wrote:
>
> Good afternoon. I write on behalf of a client that is using the AMQ REST API to try and determine when an external application has processed all the messages in a particular queue. Previously, in AMQ 5.18.1, this method would return a "204 No Content" response but in 5.18.2 they are instead receiving "500 Server Error". Is this an intended change between the two versions?
>
> Client has provided the additional details below in the hopes that it provides some clarity:
> To check if Cycle is complete, we continue to poll the Response queue by making HTTP GET call using a URL like this - https://xxxxxxxx/activemq/api/message/xxxxxQUEUE?timeout=10&type=queue&oneShot=true
> We pass in the JMSCorrelationID in a header named "selector" with value "JMSCorrelationID='3cbcaa8a-6f38-457a-aa5d-cb260cab0ace'"
>
> Thanks in advance for any assistance at all whatsoever,
> Michael Hoyt
>
>
> ________________________________
>
> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security, AI-powered support capabilities, and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
> ______________________________________________________________________________________
>
> www.accenture.com
Re: Queue depth determination change in amq 5.18.2?
Posted by Matt Pavlovich <ma...@gmail.com>.
Hi Michaal-
Please open a JIRA on this and we can dig in. https://issues.apache.org/jira
Project: ActiveMQ
Thanks!
Matt Pavlovich
> On Oct 11, 2023, at 12:27 PM, Hoyt, Michael <mi...@accenture.com.INVALID> wrote:
>
> Good afternoon. I write on behalf of a client that is using the AMQ REST API to try and determine when an external application has processed all the messages in a particular queue. Previously, in AMQ 5.18.1, this method would return a "204 No Content" response but in 5.18.2 they are instead receiving "500 Server Error". Is this an intended change between the two versions?
>
> Client has provided the additional details below in the hopes that it provides some clarity:
> To check if Cycle is complete, we continue to poll the Response queue by making HTTP GET call using a URL like this - https://xxxxxxxx/activemq/api/message/xxxxxQUEUE?timeout=10&type=queue&oneShot=true
> We pass in the JMSCorrelationID in a header named "selector" with value "JMSCorrelationID='3cbcaa8a-6f38-457a-aa5d-cb260cab0ace'"
>
> Thanks in advance for any assistance at all whatsoever,
> Michael Hoyt
>
>
> ________________________________
>
> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security, AI-powered support capabilities, and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
> ______________________________________________________________________________________
>
> www.accenture.com