You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Matt Pavlovich <ma...@gmail.com> on 2023/04/03 13:50:18 UTC
Re: ActiveMQ / configure queues
Hello Ephemeris-
Right now, the plugin is for all queues and topics. I agree it would make sense to add this as options on DestinationPolicy.
Feel free to open up a feature request ticket — https://issues.apache.org/jira
I’ll work to add it to 5.18.x or 5.19.x
Thanks!
Matt Pavlovich
> On Mar 31, 2023, at 4:53 PM, Ephemeris Lappis <ep...@gmail.com> wrote:
>
> Hello.
>
> I guess that "zeroExpirationOverride" could force the expiration on messages, but it seems to apply to all queues/topics, right ?
>
> Is there any way to limit the plugin to few queues only ?
>
> Thanks.
>
> Regards.
>
> Ephemeris Lappis
> Le 31/03/2023 à 20:13, Matt Pavlovich a écrit :
>> Hello Ephemeris-
>>
>> I think this would do it for you:
>>
>> https://activemq.apache.org/timestampplugin
>>
>> Thanks,
>> Matt Pavlovich
>>
>>> On Mar 31, 2023, at 10:02 AM, Ephemeris Lappis <ep...@gmail.com> <ma...@gmail.com> wrote:
>>>
>>> OK. Is there a chance I find a similar configuration for the classic version ?
>>> I guess that for DLQ I can set multiple policy entries with distinct strategies.
>>> Reading the XML configuration reference, for now I didn't find any
>>> policy to force message expiration (time to live) for some queues :
>>> we'd prefer to set it in the server configuration, and not in the
>>> Camel code.
>>>
>>> Thanks again.
>>>
>>> Le ven. 31 mars 2023 à 16:36, Timothy Bish <ta...@gmail.com> <ma...@gmail.com> a écrit :
>>>> On 3/31/23 10:22, Ephemeris Lappis wrote:
>>>>> Hello.
>>>>>
>>>>> Thanks. I'm going to have a look at these configuration items. Do you
>>>>> confirm this also work for "classic" ActiveMQ (we do not use Artemis)
>>>>> ?
>>>> The configuration for ActiveMQ Classic and ActiveMQ Artemis are not
>>>> interchangeable.
>>>>
>>>>
>>>>> Regards.
>>>>>
>>>>> Le ven. 31 mars 2023 à 15:04, Dondorp, Erwin
>>>>> <er...@cgi.com.invalid> <ma...@cgi.com.invalid> a écrit :
>>>>>> See https://activemq.apache.org/components/artemis/documentation/latest/message-expiry.html
>>>>>> There are the address-parameters: min-expiry-delay and max-expiry-delay
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Ephemeris Lappis <ep...@gmail.com> <ma...@gmail.com>
>>>>>> Sent: vrijdag 31 maart 2023 15:01
>>>>>> To: users@activemq.apache.org <ma...@activemq.apache.org>
>>>>>> Subject: ActiveMQ / configure queues
>>>>>>
>>>>>>
>>>>>> EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe.
>>>>>> EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre.
>>>>>>
>>>>>> Hello.
>>>>>>
>>>>>> Is there any way to configure queues on the server side with specific settings like "time to live" for example ? The same way, I'd like to enable or disable DLQ for some queues.
>>>>>>
>>>>>> Our XML configuration already uses policies like :
>>>>>> <policyEntry queue=">" producerFlowControl="true" memoryLimit="256m"
>>>>>> queuePrefetch="1" lazyDispatch="true">
>>>>>> <deadLetterStrategy>
>>>>>> <individualDeadLetterStrategy queuePrefix="DLQ."
>>>>>> useQueueForQueueMessages="true"/>
>>>>>> </deadLetterStrategy>
>>>>>> </policyEntry>
>>>>>>
>>>>>> Can I set similar policies to exclude DLQ for queues with a given pattern, and setting a time to live ?
>>>>>>
>>>>>> For example, if I set a first policy with queue="PREFIX1.>" without DLQ strategy, is the other policy applied to other queues ?
>>>>>>
>>>>>> Thanks in advance for your help.
>>>>>>
>>>>>> Regards.
>>>>
>>>> --
>>>> Tim Bish
>>>>
>>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Sans virus.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <x-msg://10/#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Re: ActiveMQ / configure queues
Posted by Matt Pavlovich <ma...@gmail.com>.
Thanks, Ephemeris!
I’ve taken assignment and will work to get it implemented.
Thanks,
Matt
> On Apr 4, 2023, at 6:50 AM, Ephemeris Lappis <ep...@gmail.com> wrote:
>
> Hello Matt.
>
> Here is the ticket : https://issues.apache.org/jira/browse/AMQ-9240.
>
> Thanks again.
>
> Regards.
>
>
> Le lun. 3 avr. 2023 à 15:50, Matt Pavlovich <mattrpav@gmail.com <ma...@gmail.com>> a écrit :
>> Hello Ephemeris-
>>
>> Right now, the plugin is for all queues and topics. I agree it would make sense to add this as options on DestinationPolicy.
>>
>> Feel free to open up a feature request ticket — https://issues.apache.org/jira
>>
>> I’ll work to add it to 5.18.x or 5.19.x
>>
>> Thanks!
>> Matt Pavlovich
>>
>>> On Mar 31, 2023, at 4:53 PM, Ephemeris Lappis <ephemeris.lappis@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Hello.
>>>
>>> I guess that "zeroExpirationOverride" could force the expiration on messages, but it seems to apply to all queues/topics, right ?
>>>
>>> Is there any way to limit the plugin to few queues only ?
>>>
>>> Thanks.
>>>
>>> Regards.
>>>
>>> Ephemeris Lappis
>>> Le 31/03/2023 à 20:13, Matt Pavlovich a écrit :
>>>> Hello Ephemeris-
>>>>
>>>> I think this would do it for you:
>>>>
>>>> https://activemq.apache.org/timestampplugin
>>>>
>>>> Thanks,
>>>> Matt Pavlovich
>>>>
>>>>> On Mar 31, 2023, at 10:02 AM, Ephemeris Lappis <ep...@gmail.com> <ma...@gmail.com> wrote:
>>>>>
>>>>> OK. Is there a chance I find a similar configuration for the classic version ?
>>>>> I guess that for DLQ I can set multiple policy entries with distinct strategies.
>>>>> Reading the XML configuration reference, for now I didn't find any
>>>>> policy to force message expiration (time to live) for some queues :
>>>>> we'd prefer to set it in the server configuration, and not in the
>>>>> Camel code.
>>>>>
>>>>> Thanks again.
>>>>>
>>>>> Le ven. 31 mars 2023 à 16:36, Timothy Bish <ta...@gmail.com> <ma...@gmail.com> a écrit :
>>>>>> On 3/31/23 10:22, Ephemeris Lappis wrote:
>>>>>>> Hello.
>>>>>>>
>>>>>>> Thanks. I'm going to have a look at these configuration items. Do you
>>>>>>> confirm this also work for "classic" ActiveMQ (we do not use Artemis)
>>>>>>> ?
>>>>>> The configuration for ActiveMQ Classic and ActiveMQ Artemis are not
>>>>>> interchangeable.
>>>>>>
>>>>>>
>>>>>>> Regards.
>>>>>>>
>>>>>>> Le ven. 31 mars 2023 à 15:04, Dondorp, Erwin
>>>>>>> <er...@cgi.com.invalid> <ma...@cgi.com.invalid> a écrit :
>>>>>>>> See https://activemq.apache.org/components/artemis/documentation/latest/message-expiry.html
>>>>>>>> There are the address-parameters: min-expiry-delay and max-expiry-delay
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Ephemeris Lappis <ep...@gmail.com> <ma...@gmail.com>
>>>>>>>> Sent: vrijdag 31 maart 2023 15:01
>>>>>>>> To: users@activemq.apache.org <ma...@activemq.apache.org>
>>>>>>>> Subject: ActiveMQ / configure queues
>>>>>>>>
>>>>>>>>
>>>>>>>> EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe.
>>>>>>>> EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre.
>>>>>>>>
>>>>>>>> Hello.
>>>>>>>>
>>>>>>>> Is there any way to configure queues on the server side with specific settings like "time to live" for example ? The same way, I'd like to enable or disable DLQ for some queues.
>>>>>>>>
>>>>>>>> Our XML configuration already uses policies like :
>>>>>>>> <policyEntry queue=">" producerFlowControl="true" memoryLimit="256m"
>>>>>>>> queuePrefetch="1" lazyDispatch="true">
>>>>>>>> <deadLetterStrategy>
>>>>>>>> <individualDeadLetterStrategy queuePrefix="DLQ."
>>>>>>>> useQueueForQueueMessages="true"/>
>>>>>>>> </deadLetterStrategy>
>>>>>>>> </policyEntry>
>>>>>>>>
>>>>>>>> Can I set similar policies to exclude DLQ for queues with a given pattern, and setting a time to live ?
>>>>>>>>
>>>>>>>> For example, if I set a first policy with queue="PREFIX1.>" without DLQ strategy, is the other policy applied to other queues ?
>>>>>>>>
>>>>>>>> Thanks in advance for your help.
>>>>>>>>
>>>>>>>> Regards.
>>>>>> --
>>>>>> Tim Bish
>>>>>>
>>>
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Sans virus.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Re: ActiveMQ / configure queues
Posted by Ephemeris Lappis <ep...@gmail.com>.
Hello Matt.
Here is the ticket : https://issues.apache.org/jira/browse/AMQ-9240.
Thanks again.
Regards.
Le lun. 3 avr. 2023 à 15:50, Matt Pavlovich <ma...@gmail.com> a écrit :
> Hello Ephemeris-
>
> Right now, the plugin is for all queues and topics. I agree it would make
> sense to add this as options on DestinationPolicy.
>
> Feel free to open up a feature request ticket —
> https://issues.apache.org/jira
>
> I’ll work to add it to 5.18.x or 5.19.x
>
> Thanks!
> Matt Pavlovich
>
> On Mar 31, 2023, at 4:53 PM, Ephemeris Lappis <ep...@gmail.com>
> wrote:
>
> Hello.
>
> I guess that "zeroExpirationOverride" could force the expiration on
> messages, but it seems to apply to all queues/topics, right ?
>
> Is there any way to limit the plugin to few queues only ?
>
> Thanks.
>
> Regards.
>
> Ephemeris Lappis
>
> Le 31/03/2023 à 20:13, Matt Pavlovich a écrit :
>
> Hello Ephemeris-
>
> I think this would do it for you:
> https://activemq.apache.org/timestampplugin
>
> Thanks,
> Matt Pavlovich
>
>
> On Mar 31, 2023, at 10:02 AM, Ephemeris Lappis <ep...@gmail.com> <ep...@gmail.com> wrote:
>
> OK. Is there a chance I find a similar configuration for the classic version ?
> I guess that for DLQ I can set multiple policy entries with distinct strategies.
> Reading the XML configuration reference, for now I didn't find any
> policy to force message expiration (time to live) for some queues :
> we'd prefer to set it in the server configuration, and not in the
> Camel code.
>
> Thanks again.
>
> Le ven. 31 mars 2023 à 16:36, Timothy Bish <ta...@gmail.com> <ta...@gmail.com> a écrit :
>
> On 3/31/23 10:22, Ephemeris Lappis wrote:
>
> Hello.
>
> Thanks. I'm going to have a look at these configuration items. Do you
> confirm this also work for "classic" ActiveMQ (we do not use Artemis)
> ?
>
> The configuration for ActiveMQ Classic and ActiveMQ Artemis are not
> interchangeable.
>
>
>
> Regards.
>
> Le ven. 31 mars 2023 à 15:04, Dondorp, Erwin<er...@cgi.com.invalid> <er...@cgi.com.invalid> a écrit :
>
> See https://activemq.apache.org/components/artemis/documentation/latest/message-expiry.html
> There are the address-parameters: min-expiry-delay and max-expiry-delay
>
> -----Original Message-----
> From: Ephemeris Lappis <ep...@gmail.com> <ep...@gmail.com>
> Sent: vrijdag 31 maart 2023 15:01
> To: users@activemq.apache.org
> Subject: ActiveMQ / configure queues
>
>
> EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe.
> EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre.
>
> Hello.
>
> Is there any way to configure queues on the server side with specific settings like "time to live" for example ? The same way, I'd like to enable or disable DLQ for some queues.
>
> Our XML configuration already uses policies like :
> <policyEntry queue=">" producerFlowControl="true" memoryLimit="256m"
> queuePrefetch="1" lazyDispatch="true">
> <deadLetterStrategy>
> <individualDeadLetterStrategy queuePrefix="DLQ."
> useQueueForQueueMessages="true"/>
> </deadLetterStrategy>
> </policyEntry>
>
> Can I set similar policies to exclude DLQ for queues with a given pattern, and setting a time to live ?
>
> For example, if I set a first policy with queue="PREFIX1.>" without DLQ strategy, is the other policy applied to other queues ?
>
> Thanks in advance for your help.
>
> Regards.
>
> --
> Tim Bish
>
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Sans
> virus.www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>
>
>
Re: ActiveMQ / configure queues
Posted by Ephemeris Lappis <ep...@gmail.com>.
Hello.
OK, I'll open a ticket to add queue specific policies.
For now, please could you confirm that these two entries, in the given
order, lead to moving failing messages to DLQ for any queue, except for
queues with a name that matches the pattern "noread.*", deleting expired
messages directly ?
<policyEntry queue=">" producerFlowControl="true" memoryLimit="256m"
queuePrefetch="1" lazyDispatch="true">
<deadLetterStrategy>
<individualDeadLetterStrategy queuePrefix="DLQ."
useQueueForQueueMessages="true" processExpired="false"/>
</deadLetterStrategy>
</policyEntry>
<policyEntry queue="noread.*" producerFlowControl="true" memoryLimit="256m"
queuePrefetch="1" lazyDispatch="true">
<deadLetterStrategy>
<sharedDeadLetterStrategy processExpired="false" />
</deadLetterStrategy>
</policyEntry>
Thanks again.
Regards.
Le lun. 3 avr. 2023 à 15:50, Matt Pavlovich <ma...@gmail.com> a écrit :
> Hello Ephemeris-
>
> Right now, the plugin is for all queues and topics. I agree it would make
> sense to add this as options on DestinationPolicy.
>
> Feel free to open up a feature request ticket —
> https://issues.apache.org/jira
>
> I’ll work to add it to 5.18.x or 5.19.x
>
> Thanks!
> Matt Pavlovich
>
> On Mar 31, 2023, at 4:53 PM, Ephemeris Lappis <ep...@gmail.com>
> wrote:
>
> Hello.
>
> I guess that "zeroExpirationOverride" could force the expiration on
> messages, but it seems to apply to all queues/topics, right ?
>
> Is there any way to limit the plugin to few queues only ?
>
> Thanks.
>
> Regards.
>
> Ephemeris Lappis
>
> Le 31/03/2023 à 20:13, Matt Pavlovich a écrit :
>
> Hello Ephemeris-
>
> I think this would do it for you:
> https://activemq.apache.org/timestampplugin
>
> Thanks,
> Matt Pavlovich
>
>
> On Mar 31, 2023, at 10:02 AM, Ephemeris Lappis <ep...@gmail.com> <ep...@gmail.com> wrote:
>
> OK. Is there a chance I find a similar configuration for the classic version ?
> I guess that for DLQ I can set multiple policy entries with distinct strategies.
> Reading the XML configuration reference, for now I didn't find any
> policy to force message expiration (time to live) for some queues :
> we'd prefer to set it in the server configuration, and not in the
> Camel code.
>
> Thanks again.
>
> Le ven. 31 mars 2023 à 16:36, Timothy Bish <ta...@gmail.com> <ta...@gmail.com> a écrit :
>
> On 3/31/23 10:22, Ephemeris Lappis wrote:
>
> Hello.
>
> Thanks. I'm going to have a look at these configuration items. Do you
> confirm this also work for "classic" ActiveMQ (we do not use Artemis)
> ?
>
> The configuration for ActiveMQ Classic and ActiveMQ Artemis are not
> interchangeable.
>
>
>
> Regards.
>
> Le ven. 31 mars 2023 à 15:04, Dondorp, Erwin<er...@cgi.com.invalid> <er...@cgi.com.invalid> a écrit :
>
> See https://activemq.apache.org/components/artemis/documentation/latest/message-expiry.html
> There are the address-parameters: min-expiry-delay and max-expiry-delay
>
> -----Original Message-----
> From: Ephemeris Lappis <ep...@gmail.com> <ep...@gmail.com>
> Sent: vrijdag 31 maart 2023 15:01
> To: users@activemq.apache.org
> Subject: ActiveMQ / configure queues
>
>
> EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe.
> EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre.
>
> Hello.
>
> Is there any way to configure queues on the server side with specific settings like "time to live" for example ? The same way, I'd like to enable or disable DLQ for some queues.
>
> Our XML configuration already uses policies like :
> <policyEntry queue=">" producerFlowControl="true" memoryLimit="256m"
> queuePrefetch="1" lazyDispatch="true">
> <deadLetterStrategy>
> <individualDeadLetterStrategy queuePrefix="DLQ."
> useQueueForQueueMessages="true"/>
> </deadLetterStrategy>
> </policyEntry>
>
> Can I set similar policies to exclude DLQ for queues with a given pattern, and setting a time to live ?
>
> For example, if I set a first policy with queue="PREFIX1.>" without DLQ strategy, is the other policy applied to other queues ?
>
> Thanks in advance for your help.
>
> Regards.
>
> --
> Tim Bish
>
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Sans
> virus.www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>
>
>