You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Christopher Pisz <ch...@gmail.com> on 2021/04/13 21:15:47 UTC
all anycast except for one multicast
Is there a way for me to config broker.xml using the wild card for any
queue without having to name them all, make them anycast with specific dead
letter queues and times, but then specify one queue with a specific name,
which has its own setting and is uneffected by the wildcard settings?
Anyone have a small snippet of what that might look like?
Re: all anycast except for one multicast
Posted by Justin Bertram <jb...@apache.org>.
> I wish I didn't have to repeat the config specific to "a" and "b", that I
don't want for "a.maintenance"
Why not do something like this:
<!-- these settings apply to /queue/a and /queue/b -->
<address-setting match="/queue/#">
<expiry-address>ExpiryAddress</expiry-address>
<auto-create-expiry-resources>true</auto-create-expiry-resources>
<expiry-queue-prefix></expiry-queue-prefix>
<expiry-queue-suffix>.EXP</expiry-queue-suffix>
<expiry-delay>120000</expiry-delay>
<dead-letter-address>DLQ</dead-letter-address>
<redelivery-delay>5000</redelivery-delay>
<max-delivery-attempts>3</max-delivery-attempts>
<max-size-bytes>104857600</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>FAIL</address-full-policy>
<auto-create-queues>false</auto-create-queues>
<auto-create-addresses>false</auto-create-addresses>
<auto-create-jms-queues>false</auto-create-jms-queues>
<auto-create-jms-topics>false</auto-create-jms-topics>
</address-setting>
<!-- these settings only apply to /queue/a.maintenance -->
<address-setting match="/queue/a.maintenance">
...
</address-setting>
Keep in mind that address-settings are *heirarchical*. You can have more
general and more specific matches so you don't have to repeat the same
configuration multiple times.
Justin
On Tue, Apr 13, 2021 at 9:57 PM Christopher Pisz <ch...@gmail.com>
wrote:
> I think I got something that works through reading, trial, and error, but I
> wish I didn't have to repeat the config specific to "a" and "b", that I
> don't want for "a.maintenance"
>
> Also, when looking at the console management tool, I see queues being made
> with hex names under the multicast address when I subscribe or send a
> message through STOMP, but the behavior seems correct and it send it to all
> clients, then deletes those queues when consumers leave. The desire if you
> guys can verify for me, is that we don't want any messages lingering in
> that queue. When our tool connects, we want one at most, although none is
> fine, until a new one arrives.
>
> <address-settings>
> <address-setting match="activemq.management#">
> <expiry-address>ExpiryAddress</expiry-address>
>
> <auto-create-expiry-resources>true</auto-create-expiry-resources>
> <expiry-queue-prefix></expiry-queue-prefix>
> <expiry-queue-suffix>.EXP</expiry-queue-suffix>
> <expiry-delay>120000</expiry-delay>
> <dead-letter-address>DLQ</dead-letter-address>
> <redelivery-delay>0</redelivery-delay>
> <max-size-bytes>104857600</max-size-bytes>
>
> <message-counter-history-day-limit>10</message-counter-history-day-limit>
> <address-full-policy>FAIL</address-full-policy>
> <auto-create-queues>true</auto-create-queues>
> <auto-create-addresses>true</auto-create-addresses>
> <auto-create-jms-queues>true</auto-create-jms-queues>
> <auto-create-jms-topics>true</auto-create-jms-topics>
> </address-setting>
> <address-setting match="/queue/a">
> <expiry-address>ExpiryAddress</expiry-address>
>
> <auto-create-expiry-resources>true</auto-create-expiry-resources>
> <expiry-queue-prefix></expiry-queue-prefix>
> <expiry-queue-suffix>.EXP</expiry-queue-suffix>
> <expiry-delay>120000</expiry-delay>
> <dead-letter-address>DLQ</dead-letter-address>
> <redelivery-delay>5000</redelivery-delay>
> <max-delivery-attempts>3</max-delivery-attempts>
> <max-size-bytes>104857600</max-size-bytes>
>
> <message-counter-history-day-limit>10</message-counter-history-day-limit>
> <address-full-policy>FAIL</address-full-policy>
> <auto-create-queues>false</auto-create-queues>
> <auto-create-addresses>false</auto-create-addresses>
> <auto-create-jms-queues>false</auto-create-jms-queues>
> <auto-create-jms-topics>false</auto-create-jms-topics>
> </address-setting>
> <address-setting match="/queue/b">
> <expiry-address>ExpiryAddress</expiry-address>
>
> <auto-create-expiry-resources>true</auto-create-expiry-resources>
> <expiry-queue-prefix></expiry-queue-prefix>
> <expiry-queue-suffix>.EXP</expiry-queue-suffix>
> <expiry-delay>120000</expiry-delay>
> <dead-letter-address>DLQ</dead-letter-address>
> <redelivery-delay>5000</redelivery-delay>
> <max-delivery-attempts>3</max-delivery-attempts>
> <max-size-bytes>104857600</max-size-bytes>
>
> <message-counter-history-day-limit>10</message-counter-history-day-limit>
> <address-full-policy>FAIL</address-full-policy>
> <auto-create-queues>false</auto-create-queues>
> <auto-create-addresses>false</auto-create-addresses>
> <auto-create-jms-queues>false</auto-create-jms-queues>
> <auto-create-jms-topics>false</auto-create-jms-topics>
> </address-setting>
> </address-settings>
>
> <addresses>
> <address name="/queue/a.maintenance">
> <multicast>
> <queue name="/queue/a.maintenance"
> purge-on-no-consumers="true"/>
> </multicast>
> </address>
> <address name="/queue/a">
> <anycast>
> <queue name="/queue/a"/>
> </anycast>
> </address>
> <address name="/queue/b">
> <anycast>
> <queue name="/queue/b"/>
> </anycast>
> </address>
> <address name="DLQ">
> <anycast>
> <queue name="DLQ" />
> </anycast>
> </address>
> </addresses>
>
>
>
> On Tue, Apr 13, 2021 at 7:46 PM Christopher Pisz <
> christopherpisz@gmail.com>
> wrote:
>
> > reading through the docs, I try adding something like
> >
> > <address name="pubsub.maintenance" purge-on-no-consumers="true">
> > <multicast/>
> > </address>
> >
> > to the addresses section, but when I start up my STOMP client and
> subscribe to "pubsub.maintenance", in the management console, I see a
> folder, and anycast under it, with a gear icon "pubsub.maintenance" under
> that.
> >
> > I believe it applied the wildcard settings to the new queue, but I don't
> want it to.
> >
> >
> > As a secondary question, I see two addresses "mystuff/hardware"
> "mystuff/customer" with gear icons next to them, directly under "addresses"
> and before any folders. Are those old addresses and it never got rid of
> them? I don't see anything with those names in my broker.xml. If so, how do
> I delete them?
> >
> >
> > On Tue, Apr 13, 2021 at 6:53 PM Christopher Pisz <
> > christopherpisz@gmail.com> wrote:
> >
> >> I currently have a config section that looks like the following and it
> >> works great, except I want to add one named queue that is multicast,
> and if
> >> no one picks up a message right away from this new queue, it throws it
> away
> >> after 1 clock minute.
> >>
> >> <address-settings>
> >> <!-- if you define auto-create on certain queues, management has to
> be auto-create -->
> >> <address-setting match="activemq.management#">
> >> <dead-letter-address>DLQ</dead-letter-address>
> >> <expiry-address>ExpiryQueue</expiry-address>
> >> <redelivery-delay>0</redelivery-delay>
> >> <!-- with -1 only the global-max-size is in use for limiting -->
> >> <max-size-bytes>-1</max-size-bytes>
> >>
> <message-counter-history-day-limit>10</message-counter-history-day-limit>
> >> <address-full-policy>PAGE</address-full-policy>
> >> <auto-create-queues>true</auto-create-queues>
> >> <auto-create-addresses>true</auto-create-addresses>
> >> <auto-create-jms-queues>true</auto-create-jms-queues>
> >> <auto-create-jms-topics>true</auto-create-jms-topics>
> >> </address-setting>
> >> <!--default for catch all-->
> >> <address-setting match="#">
> >>
> <default-address-routing-type>ANYCAST</default-address-routing-type>
> >> <default-queue-routing-type>ANYCAST</default-queue-routing-type>
> >> <expiry-address>ExpiryAddress</expiry-address>
> >> <auto-create-expiry-resources>true</auto-create-expiry-resources>
> >> <expiry-queue-prefix></expiry-queue-prefix>
> >> <expiry-queue-suffix>.EXP</expiry-queue-suffix>
> >> <expiry-delay>120000</expiry-delay>
> >> <dead-letter-address>DLQ</dead-letter-address>
> >> <redelivery-delay>5000</redelivery-delay>
> >> <max-delivery-attempts>3</max-delivery-attempts>
> >> <!-- with -1 only the global-max-size is in use for limiting -->
> >> <max-size-bytes>-1</max-size-bytes>
> >>
> <message-counter-history-day-limit>10</message-counter-history-day-limit>
> >> <address-full-policy>PAGE</address-full-policy>
> >> <auto-create-queues>true</auto-create-queues>
> >> <auto-create-addresses>true</auto-create-addresses>
> >> <auto-create-jms-queues>true</auto-create-jms-queues>
> >> <auto-create-jms-topics>true</auto-create-jms-topics>
> >> </address-setting>
> >> </address-settings>
> >>
> >> <addresses>
> >> <address name="DLQ">
> >> <anycast>
> >> <queue name="DLQ" />
> >> </anycast>
> >> </address>
> >> <address name="ExpiryQueue">
> >> <anycast>
> >> <queue name="ExpiryQueue" />
> >> </anycast>
> >> </address>
> >> </addresses>
> >>
> >>
> >> On Tue, Apr 13, 2021 at 6:40 PM Justin Bertram <jb...@apache.org>
> >> wrote:
> >>
> >>> I'm not really sure what you're asking. Let's start at the beginning...
> >>>
> >>> When you say, "...config broker.xml using the wild card for any queue
> >>> without having to name them all..." are you talking about configuring
> >>> queues via address-settings with a wildcard match like "#"?
> >>>
> >>> What do you mean "dead letter...times"? What is a "time" in this
> context?
> >>>
> >>>
> >>> Justin
> >>>
> >>> On Tue, Apr 13, 2021 at 4:16 PM Christopher Pisz <
> >>> christopherpisz@gmail.com>
> >>> wrote:
> >>>
> >>> > Is there a way for me to config broker.xml using the wild card for
> any
> >>> > queue without having to name them all, make them anycast with
> specific
> >>> dead
> >>> > letter queues and times, but then specify one queue with a specific
> >>> name,
> >>> > which has its own setting and is uneffected by the wildcard settings?
> >>> > Anyone have a small snippet of what that might look like?
> >>> >
> >>>
> >>
>
Re: all anycast except for one multicast
Posted by Christopher Pisz <ch...@gmail.com>.
I think I got something that works through reading, trial, and error, but I
wish I didn't have to repeat the config specific to "a" and "b", that I
don't want for "a.maintenance"
Also, when looking at the console management tool, I see queues being made
with hex names under the multicast address when I subscribe or send a
message through STOMP, but the behavior seems correct and it send it to all
clients, then deletes those queues when consumers leave. The desire if you
guys can verify for me, is that we don't want any messages lingering in
that queue. When our tool connects, we want one at most, although none is
fine, until a new one arrives.
<address-settings>
<address-setting match="activemq.management#">
<expiry-address>ExpiryAddress</expiry-address>
<auto-create-expiry-resources>true</auto-create-expiry-resources>
<expiry-queue-prefix></expiry-queue-prefix>
<expiry-queue-suffix>.EXP</expiry-queue-suffix>
<expiry-delay>120000</expiry-delay>
<dead-letter-address>DLQ</dead-letter-address>
<redelivery-delay>0</redelivery-delay>
<max-size-bytes>104857600</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>FAIL</address-full-policy>
<auto-create-queues>true</auto-create-queues>
<auto-create-addresses>true</auto-create-addresses>
<auto-create-jms-queues>true</auto-create-jms-queues>
<auto-create-jms-topics>true</auto-create-jms-topics>
</address-setting>
<address-setting match="/queue/a">
<expiry-address>ExpiryAddress</expiry-address>
<auto-create-expiry-resources>true</auto-create-expiry-resources>
<expiry-queue-prefix></expiry-queue-prefix>
<expiry-queue-suffix>.EXP</expiry-queue-suffix>
<expiry-delay>120000</expiry-delay>
<dead-letter-address>DLQ</dead-letter-address>
<redelivery-delay>5000</redelivery-delay>
<max-delivery-attempts>3</max-delivery-attempts>
<max-size-bytes>104857600</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>FAIL</address-full-policy>
<auto-create-queues>false</auto-create-queues>
<auto-create-addresses>false</auto-create-addresses>
<auto-create-jms-queues>false</auto-create-jms-queues>
<auto-create-jms-topics>false</auto-create-jms-topics>
</address-setting>
<address-setting match="/queue/b">
<expiry-address>ExpiryAddress</expiry-address>
<auto-create-expiry-resources>true</auto-create-expiry-resources>
<expiry-queue-prefix></expiry-queue-prefix>
<expiry-queue-suffix>.EXP</expiry-queue-suffix>
<expiry-delay>120000</expiry-delay>
<dead-letter-address>DLQ</dead-letter-address>
<redelivery-delay>5000</redelivery-delay>
<max-delivery-attempts>3</max-delivery-attempts>
<max-size-bytes>104857600</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>FAIL</address-full-policy>
<auto-create-queues>false</auto-create-queues>
<auto-create-addresses>false</auto-create-addresses>
<auto-create-jms-queues>false</auto-create-jms-queues>
<auto-create-jms-topics>false</auto-create-jms-topics>
</address-setting>
</address-settings>
<addresses>
<address name="/queue/a.maintenance">
<multicast>
<queue name="/queue/a.maintenance"
purge-on-no-consumers="true"/>
</multicast>
</address>
<address name="/queue/a">
<anycast>
<queue name="/queue/a"/>
</anycast>
</address>
<address name="/queue/b">
<anycast>
<queue name="/queue/b"/>
</anycast>
</address>
<address name="DLQ">
<anycast>
<queue name="DLQ" />
</anycast>
</address>
</addresses>
On Tue, Apr 13, 2021 at 7:46 PM Christopher Pisz <ch...@gmail.com>
wrote:
> reading through the docs, I try adding something like
>
> <address name="pubsub.maintenance" purge-on-no-consumers="true">
> <multicast/>
> </address>
>
> to the addresses section, but when I start up my STOMP client and subscribe to "pubsub.maintenance", in the management console, I see a folder, and anycast under it, with a gear icon "pubsub.maintenance" under that.
>
> I believe it applied the wildcard settings to the new queue, but I don't want it to.
>
>
> As a secondary question, I see two addresses "mystuff/hardware" "mystuff/customer" with gear icons next to them, directly under "addresses" and before any folders. Are those old addresses and it never got rid of them? I don't see anything with those names in my broker.xml. If so, how do I delete them?
>
>
> On Tue, Apr 13, 2021 at 6:53 PM Christopher Pisz <
> christopherpisz@gmail.com> wrote:
>
>> I currently have a config section that looks like the following and it
>> works great, except I want to add one named queue that is multicast, and if
>> no one picks up a message right away from this new queue, it throws it away
>> after 1 clock minute.
>>
>> <address-settings>
>> <!-- if you define auto-create on certain queues, management has to be auto-create -->
>> <address-setting match="activemq.management#">
>> <dead-letter-address>DLQ</dead-letter-address>
>> <expiry-address>ExpiryQueue</expiry-address>
>> <redelivery-delay>0</redelivery-delay>
>> <!-- with -1 only the global-max-size is in use for limiting -->
>> <max-size-bytes>-1</max-size-bytes>
>> <message-counter-history-day-limit>10</message-counter-history-day-limit>
>> <address-full-policy>PAGE</address-full-policy>
>> <auto-create-queues>true</auto-create-queues>
>> <auto-create-addresses>true</auto-create-addresses>
>> <auto-create-jms-queues>true</auto-create-jms-queues>
>> <auto-create-jms-topics>true</auto-create-jms-topics>
>> </address-setting>
>> <!--default for catch all-->
>> <address-setting match="#">
>> <default-address-routing-type>ANYCAST</default-address-routing-type>
>> <default-queue-routing-type>ANYCAST</default-queue-routing-type>
>> <expiry-address>ExpiryAddress</expiry-address>
>> <auto-create-expiry-resources>true</auto-create-expiry-resources>
>> <expiry-queue-prefix></expiry-queue-prefix>
>> <expiry-queue-suffix>.EXP</expiry-queue-suffix>
>> <expiry-delay>120000</expiry-delay>
>> <dead-letter-address>DLQ</dead-letter-address>
>> <redelivery-delay>5000</redelivery-delay>
>> <max-delivery-attempts>3</max-delivery-attempts>
>> <!-- with -1 only the global-max-size is in use for limiting -->
>> <max-size-bytes>-1</max-size-bytes>
>> <message-counter-history-day-limit>10</message-counter-history-day-limit>
>> <address-full-policy>PAGE</address-full-policy>
>> <auto-create-queues>true</auto-create-queues>
>> <auto-create-addresses>true</auto-create-addresses>
>> <auto-create-jms-queues>true</auto-create-jms-queues>
>> <auto-create-jms-topics>true</auto-create-jms-topics>
>> </address-setting>
>> </address-settings>
>>
>> <addresses>
>> <address name="DLQ">
>> <anycast>
>> <queue name="DLQ" />
>> </anycast>
>> </address>
>> <address name="ExpiryQueue">
>> <anycast>
>> <queue name="ExpiryQueue" />
>> </anycast>
>> </address>
>> </addresses>
>>
>>
>> On Tue, Apr 13, 2021 at 6:40 PM Justin Bertram <jb...@apache.org>
>> wrote:
>>
>>> I'm not really sure what you're asking. Let's start at the beginning...
>>>
>>> When you say, "...config broker.xml using the wild card for any queue
>>> without having to name them all..." are you talking about configuring
>>> queues via address-settings with a wildcard match like "#"?
>>>
>>> What do you mean "dead letter...times"? What is a "time" in this context?
>>>
>>>
>>> Justin
>>>
>>> On Tue, Apr 13, 2021 at 4:16 PM Christopher Pisz <
>>> christopherpisz@gmail.com>
>>> wrote:
>>>
>>> > Is there a way for me to config broker.xml using the wild card for any
>>> > queue without having to name them all, make them anycast with specific
>>> dead
>>> > letter queues and times, but then specify one queue with a specific
>>> name,
>>> > which has its own setting and is uneffected by the wildcard settings?
>>> > Anyone have a small snippet of what that might look like?
>>> >
>>>
>>
Re: all anycast except for one multicast
Posted by Christopher Pisz <ch...@gmail.com>.
reading through the docs, I try adding something like
<address name="pubsub.maintenance" purge-on-no-consumers="true">
<multicast/>
</address>
to the addresses section, but when I start up my STOMP client and
subscribe to "pubsub.maintenance", in the management console, I see a
folder, and anycast under it, with a gear icon "pubsub.maintenance"
under that.
I believe it applied the wildcard settings to the new queue, but I
don't want it to.
As a secondary question, I see two addresses "mystuff/hardware"
"mystuff/customer" with gear icons next to them, directly under
"addresses" and before any folders. Are those old addresses and it
never got rid of them? I don't see anything with those names in my
broker.xml. If so, how do I delete them?
On Tue, Apr 13, 2021 at 6:53 PM Christopher Pisz <ch...@gmail.com>
wrote:
> I currently have a config section that looks like the following and it
> works great, except I want to add one named queue that is multicast, and if
> no one picks up a message right away from this new queue, it throws it away
> after 1 clock minute.
>
> <address-settings>
> <!-- if you define auto-create on certain queues, management has to be auto-create -->
> <address-setting match="activemq.management#">
> <dead-letter-address>DLQ</dead-letter-address>
> <expiry-address>ExpiryQueue</expiry-address>
> <redelivery-delay>0</redelivery-delay>
> <!-- with -1 only the global-max-size is in use for limiting -->
> <max-size-bytes>-1</max-size-bytes>
> <message-counter-history-day-limit>10</message-counter-history-day-limit>
> <address-full-policy>PAGE</address-full-policy>
> <auto-create-queues>true</auto-create-queues>
> <auto-create-addresses>true</auto-create-addresses>
> <auto-create-jms-queues>true</auto-create-jms-queues>
> <auto-create-jms-topics>true</auto-create-jms-topics>
> </address-setting>
> <!--default for catch all-->
> <address-setting match="#">
> <default-address-routing-type>ANYCAST</default-address-routing-type>
> <default-queue-routing-type>ANYCAST</default-queue-routing-type>
> <expiry-address>ExpiryAddress</expiry-address>
> <auto-create-expiry-resources>true</auto-create-expiry-resources>
> <expiry-queue-prefix></expiry-queue-prefix>
> <expiry-queue-suffix>.EXP</expiry-queue-suffix>
> <expiry-delay>120000</expiry-delay>
> <dead-letter-address>DLQ</dead-letter-address>
> <redelivery-delay>5000</redelivery-delay>
> <max-delivery-attempts>3</max-delivery-attempts>
> <!-- with -1 only the global-max-size is in use for limiting -->
> <max-size-bytes>-1</max-size-bytes>
> <message-counter-history-day-limit>10</message-counter-history-day-limit>
> <address-full-policy>PAGE</address-full-policy>
> <auto-create-queues>true</auto-create-queues>
> <auto-create-addresses>true</auto-create-addresses>
> <auto-create-jms-queues>true</auto-create-jms-queues>
> <auto-create-jms-topics>true</auto-create-jms-topics>
> </address-setting>
> </address-settings>
>
> <addresses>
> <address name="DLQ">
> <anycast>
> <queue name="DLQ" />
> </anycast>
> </address>
> <address name="ExpiryQueue">
> <anycast>
> <queue name="ExpiryQueue" />
> </anycast>
> </address>
> </addresses>
>
>
> On Tue, Apr 13, 2021 at 6:40 PM Justin Bertram <jb...@apache.org>
> wrote:
>
>> I'm not really sure what you're asking. Let's start at the beginning...
>>
>> When you say, "...config broker.xml using the wild card for any queue
>> without having to name them all..." are you talking about configuring
>> queues via address-settings with a wildcard match like "#"?
>>
>> What do you mean "dead letter...times"? What is a "time" in this context?
>>
>>
>> Justin
>>
>> On Tue, Apr 13, 2021 at 4:16 PM Christopher Pisz <
>> christopherpisz@gmail.com>
>> wrote:
>>
>> > Is there a way for me to config broker.xml using the wild card for any
>> > queue without having to name them all, make them anycast with specific
>> dead
>> > letter queues and times, but then specify one queue with a specific
>> name,
>> > which has its own setting and is uneffected by the wildcard settings?
>> > Anyone have a small snippet of what that might look like?
>> >
>>
>
Re: all anycast except for one multicast
Posted by Christopher Pisz <ch...@gmail.com>.
I currently have a config section that looks like the following and it
works great, except I want to add one named queue that is multicast, and if
no one picks up a message right away from this new queue, it throws it away
after 1 clock minute.
<address-settings>
<!-- if you define auto-create on certain queues, management has to
be auto-create -->
<address-setting match="activemq.management#">
<dead-letter-address>DLQ</dead-letter-address>
<expiry-address>ExpiryQueue</expiry-address>
<redelivery-delay>0</redelivery-delay>
<!-- with -1 only the global-max-size is in use for limiting -->
<max-size-bytes>-1</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>PAGE</address-full-policy>
<auto-create-queues>true</auto-create-queues>
<auto-create-addresses>true</auto-create-addresses>
<auto-create-jms-queues>true</auto-create-jms-queues>
<auto-create-jms-topics>true</auto-create-jms-topics>
</address-setting>
<!--default for catch all-->
<address-setting match="#">
<default-address-routing-type>ANYCAST</default-address-routing-type>
<default-queue-routing-type>ANYCAST</default-queue-routing-type>
<expiry-address>ExpiryAddress</expiry-address>
<auto-create-expiry-resources>true</auto-create-expiry-resources>
<expiry-queue-prefix></expiry-queue-prefix>
<expiry-queue-suffix>.EXP</expiry-queue-suffix>
<expiry-delay>120000</expiry-delay>
<dead-letter-address>DLQ</dead-letter-address>
<redelivery-delay>5000</redelivery-delay>
<max-delivery-attempts>3</max-delivery-attempts>
<!-- with -1 only the global-max-size is in use for limiting -->
<max-size-bytes>-1</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>PAGE</address-full-policy>
<auto-create-queues>true</auto-create-queues>
<auto-create-addresses>true</auto-create-addresses>
<auto-create-jms-queues>true</auto-create-jms-queues>
<auto-create-jms-topics>true</auto-create-jms-topics>
</address-setting>
</address-settings>
<addresses>
<address name="DLQ">
<anycast>
<queue name="DLQ" />
</anycast>
</address>
<address name="ExpiryQueue">
<anycast>
<queue name="ExpiryQueue" />
</anycast>
</address>
</addresses>
On Tue, Apr 13, 2021 at 6:40 PM Justin Bertram <jb...@apache.org> wrote:
> I'm not really sure what you're asking. Let's start at the beginning...
>
> When you say, "...config broker.xml using the wild card for any queue
> without having to name them all..." are you talking about configuring
> queues via address-settings with a wildcard match like "#"?
>
> What do you mean "dead letter...times"? What is a "time" in this context?
>
>
> Justin
>
> On Tue, Apr 13, 2021 at 4:16 PM Christopher Pisz <
> christopherpisz@gmail.com>
> wrote:
>
> > Is there a way for me to config broker.xml using the wild card for any
> > queue without having to name them all, make them anycast with specific
> dead
> > letter queues and times, but then specify one queue with a specific name,
> > which has its own setting and is uneffected by the wildcard settings?
> > Anyone have a small snippet of what that might look like?
> >
>
Re: all anycast except for one multicast
Posted by Justin Bertram <jb...@apache.org>.
I'm not really sure what you're asking. Let's start at the beginning...
When you say, "...config broker.xml using the wild card for any queue
without having to name them all..." are you talking about configuring
queues via address-settings with a wildcard match like "#"?
What do you mean "dead letter...times"? What is a "time" in this context?
Justin
On Tue, Apr 13, 2021 at 4:16 PM Christopher Pisz <ch...@gmail.com>
wrote:
> Is there a way for me to config broker.xml using the wild card for any
> queue without having to name them all, make them anycast with specific dead
> letter queues and times, but then specify one queue with a specific name,
> which has its own setting and is uneffected by the wildcard settings?
> Anyone have a small snippet of what that might look like?
>