I have set up individual dead letter strategy, however still it sends the
message to "ActiveMQ.DLQ" and not to individual DLQ queue. please guide
Vadim Pesochinsky wrote:
> You do not need to set it up, if queue does not exist when you connect to it,
> it will be created. I think by default the is
> used, i.e. all expired messages from all queues go to the same ActiveMQ.DLQ
> queue.
The individual strategy has this nice feature where it ch
You do not need to set it up, if queue does not exist when you connect to it,
it will be created. I think by default the is
used, i.e. all expired messages from all queues go to the same ActiveMQ.DLQ
queue.
--
View this message in context:
http://www.nabble.com/Expired-Message-Listener-tf327091
Use the 4.2-SNAPSHOT, not the 4.2-incubator-SNAPSHOT. (Now that we
have graduated from the Incubator we no longer use incubator in
version numbers)
On 2/23/07, manav <[EMAIL PROTECTED]> wrote:
Any ideas if this is fixed in any latest development build? I see a
4.2-SNAPSHOT and 4.2-incubator-sn
This isn't fixed in 4.2 yet either I'm afraid :(
On 23 Feb 2007, at 18:13, manav wrote:
Any ideas if this is fixed in any latest development build? I see a
4.2-SNAPSHOT and 4.2-incubator-snapshot under the 'source' link..
Not sure
how 'incubator' build is different from the other one.. but
This doesn't work correctly in 4.x at the moment. Please could you raise a
jira issue for it
cheers,
Rob
manav wrote:
>
> We recently migrated our application from ActiveMQ3.2.1 to ActiveMQ 4.1.0.
>
> We were using a listener for Expired messages (after timetolive) when we
> used ActiveMQ 3.
manav wrote:
> Any ideas if this is fixed in any latest development build? I see a
> 4.2-SNAPSHOT and 4.2-incubator-snapshot under the 'source' link.. Not sure
> how 'incubator' build is different from the other one.. but am ready to try
> anything if it is fixed...
>
>
> Christopher G. Stach
Any ideas if this is fixed in any latest development build? I see a
4.2-SNAPSHOT and 4.2-incubator-snapshot under the 'source' link.. Not sure
how 'incubator' build is different from the other one.. but am ready to try
anything if it is fixed...
Christopher G. Stach II wrote:
>
> manav wrote
manav wrote:
> Thanks for this message.. Could you please elaborate on this..
>
> Do we need to setup a queue named "ActiveMQ.DLQ" and point all our
> destinations that could have messages expired to the "ActiveMQ.DLQ" queue?
> Do you have any specific pointers / examples for this?
>
> Apprecia
Thanks for this message.. Could you please elaborate on this..
Do we need to setup a queue named "ActiveMQ.DLQ" and point all our
destinations that could have messages expired to the "ActiveMQ.DLQ" queue?
Do you have any specific pointers / examples for this?
Appreciate any help...
Manav
V
manav wrote:
> Could someone pease respond back to the posted question?
>
> We are holding off a release as we cannot get (do not know how to get)
> message expiry to work in 4.1. This is critical to a big company using AMQ.
>
> Any immediate help / suggestion is appreciated.
>
> Manav
>
>
I
I think you can use JMS api, the queue name is "ActiveMQ.DLQ" if I remember
correctly.
--
View this message in context:
http://www.nabble.com/Expired-Message-Listener-tf3270915s2354.html#a9111825
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Could someone pease respond back to the posted question?
We are holding off a release as we cannot get (do not know how to get)
message expiry to work in 4.1. This is critical to a big company using AMQ.
Any immediate help / suggestion is appreciated.
Manav
manav wrote:
>
> We recently mig
13 matches
Mail list logo
