You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by praneethg <pr...@concur.com> on 2017/07/17 19:37:40 UTC
Artemis - Wild card - messages received but not acknowledged
I have a consumer running and listening to aes.q.#,
Messages sent to aes.q.1 , aes.q.2 are consumed by consumer but not
acknowledged. Message still remains in queue.
But if i listen to those specific queues aes.q.1, then message is received
and acknowledged.
any one using wild card on the consumer side for artemis?
--
View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-Wild-card-messages-received-but-not-acknowledged-tp4728617.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Artemis - Wild card - messages received but not acknowledged
Posted by Justin Bertram <jb...@apache.org>.
Coming back to this after a discussion on ARTEMIS-2375 [1]...
I believe you're seeing the expected behavior. Messages sent to any address
matching the wildcard address will be routed to the wildcard address'
queues and those messages are acknowledged independently of the messages
routed to the particular address' queues where they were originally sent.
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS-2375
On Mon, Jul 17, 2017 at 3:06 PM Justin Bertram <jb...@redhat.com> wrote:
> A reproducible test-case is always the best way to get help on issues like
> this. Artemis ships with lots of examples. It's typically fairly trivial
> to modify one of those examples to reproduce straight-forward use-cases.
> You can share the modified example via your GitHub repo. Could you work up
> something like this? At the very least could you provide specific
> steps/code/configuration to reproduce even if it isn't automated?
>
>
> Justin
>
> On Mon, Jul 17, 2017 at 3:37 PM, praneethg <pr...@concur.com>
> wrote:
>
>> I have a consumer running and listening to aes.q.#,
>> Messages sent to aes.q.1 , aes.q.2 are consumed by consumer but not
>> acknowledged. Message still remains in queue.
>> But if i listen to those specific queues aes.q.1, then message is received
>> and acknowledged.
>>
>> any one using wild card on the consumer side for artemis?
>>
>>
>>
>> --
>> View this message in context:
>> http://activemq.2283324.n4.nabble.com/Artemis-Wild-card-messages-received-but-not-acknowledged-tp4728617.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
>
Re: Artemis - Wild card - messages received but not acknowledged
Posted by Justin Bertram <jb...@redhat.com>.
A reproducible test-case is always the best way to get help on issues like
this. Artemis ships with lots of examples. It's typically fairly trivial
to modify one of those examples to reproduce straight-forward use-cases.
You can share the modified example via your GitHub repo. Could you work up
something like this? At the very least could you provide specific
steps/code/configuration to reproduce even if it isn't automated?
Justin
On Mon, Jul 17, 2017 at 3:37 PM, praneethg <pr...@concur.com>
wrote:
> I have a consumer running and listening to aes.q.#,
> Messages sent to aes.q.1 , aes.q.2 are consumed by consumer but not
> acknowledged. Message still remains in queue.
> But if i listen to those specific queues aes.q.1, then message is received
> and acknowledged.
>
> any one using wild card on the consumer side for artemis?
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Artemis-Wild-card-messages-received-but-not-
> acknowledged-tp4728617.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>