Re: Older Message Not Consumed(Stay Untouched in queue) Newer Messages consumed

[Quinn Stevenson]

Sorry - the weren’t really shuffled.

I don’t know exactly if they were moved to the back of the queue or just held 
until their redelivery delay expired and then re-injected into the queue.  We 
didn’t test enough to make that determination - we stopped as soon as we 
discovered that delayed redelivery on the broker side broke FIFO.



> On Apr 3, 2018, at 9:59 PM, Tim Bain  wrote:
> 
> When you say "shuffled", do you simply mean that the message went to the
> back of the queue when it got sent back for broker-side redelivery? Or do
> you mean that actual randomization of all messages on the queue occurred?
> 
> Tim
> 
> On Tue, Apr 3, 2018 at 8:29 AM, Quinn Stevenson > wrote:
> 
>> No - we weren’t using selectors.  The only “special” feature we were using
>> was Virtual Topics - we saw the order shuffled on the queues created for
>> the Virtual Topic Consumers.
>> 
>> 
>>> On Apr 2, 2018, at 11:20 PM, Tim Bain  wrote:
>>> 
>>> @RuralHunter, same question as to the OP: were you using selectors? Was
>> it
>>> possible that no consumer with a selector matching those messages was
>>> online, and then one came online and consumed the message?
>>> 
>>> Tim
>>> 
>>> On Mon, Mar 26, 2018 at 8:31 AM, RuralHunter 
>> wrote:
>>> 
 I reported the same problem for 5.13.4.
 http://activemq.2283324.n4.nabble.com/Message-stuck-in-
 queue-td4720713.html
 
 
 
 --
 Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
 f2341805.html
 
>> 
>> 

Re: Older Message Not Consumed(Stay Untouched in queue) Newer Messages consumed

[Tim Bain]

When you say "shuffled", do you simply mean that the message went to the
back of the queue when it got sent back for broker-side redelivery? Or do
you mean that actual randomization of all messages on the queue occurred?

Tim

On Tue, Apr 3, 2018 at 8:29 AM, Quinn Stevenson  wrote:

> No - we weren’t using selectors.  The only “special” feature we were using
> was Virtual Topics - we saw the order shuffled on the queues created for
> the Virtual Topic Consumers.
>
>
> > On Apr 2, 2018, at 11:20 PM, Tim Bain  wrote:
> >
> > @RuralHunter, same question as to the OP: were you using selectors? Was
> it
> > possible that no consumer with a selector matching those messages was
> > online, and then one came online and consumed the message?
> >
> > Tim
> >
> > On Mon, Mar 26, 2018 at 8:31 AM, RuralHunter 
> wrote:
> >
> >> I reported the same problem for 5.13.4.
> >> http://activemq.2283324.n4.nabble.com/Message-stuck-in-
> >> queue-td4720713.html
> >>
> >>
> >>
> >> --
> >> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> >> f2341805.html
> >>
>
>

Re: Older Message Not Consumed(Stay Untouched in queue) Newer Messages consumed

[Quinn Stevenson]

No - we weren’t using selectors.  The only “special” feature we were using was 
Virtual Topics - we saw the order shuffled on the queues created for the 
Virtual Topic Consumers.


> On Apr 2, 2018, at 11:20 PM, Tim Bain  wrote:
> 
> @RuralHunter, same question as to the OP: were you using selectors? Was it
> possible that no consumer with a selector matching those messages was
> online, and then one came online and consumed the message?
> 
> Tim
> 
> On Mon, Mar 26, 2018 at 8:31 AM, RuralHunter  wrote:
> 
>> I reported the same problem for 5.13.4.
>> http://activemq.2283324.n4.nabble.com/Message-stuck-in-
>> queue-td4720713.html
>> 
>> 
>> 
>> --
>> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
>> f2341805.html
>> 

Re: Older Message Not Consumed(Stay Untouched in queue) Newer Messages consumed

[Tim Bain]

@RuralHunter, same question as to the OP: were you using selectors? Was it
possible that no consumer with a selector matching those messages was
online, and then one came online and consumed the message?

Tim

On Mon, Mar 26, 2018 at 8:31 AM, RuralHunter  wrote:

> I reported the same problem for 5.13.4.
> http://activemq.2283324.n4.nabble.com/Message-stuck-in-
> queue-td4720713.html
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>

Re: Older Message Not Consumed(Stay Untouched in queue) Newer Messages consumed

[Quinn Stevenson]

I don’t know if it’s related, but we were seeing something that sounds like 
this when we setup the ActiveMQ broker for delayed redelivery.  

What we observed was when a message was rolled-back to the broker and the delay 
started, the next message on the queue would be delivered to the consumer.  
This was on an older version of ActiveMQ (5.11) and I didn’t really go much 
further than this - I moved the redelivery handling to the client side.


> On Mar 26, 2018, at 8:31 AM, RuralHunter  wrote:
> 
> I reported the same problem for 5.13.4.
> http://activemq.2283324.n4.nabble.com/Message-stuck-in-queue-td4720713.html
> 
> 
> 
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Older Message Not Consumed(Stay Untouched in queue) Newer Messages consumed

[RuralHunter]

I reported the same problem for 5.13.4.
http://activemq.2283324.n4.nabble.com/Message-stuck-in-queue-td4720713.html



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Older Message Not Consumed(Stay Untouched in queue) Newer Messages consumed

[Tim Bain]

Do the consumers on that queue use selectors? If so, is it possible that
the selectors for all active consumers simply don't match those messages?

Does the problem persist after you restart the broker? Or are all messages
consumed once the process is restarted? In earlier versions there were some
problems where messages would not get dispatched due to a bug but would be
handled correctly after a restart, though my memory is that those problems
were primarily in the 5.8-5.10 timeframe and I don't remember having seen
reports of them in the more recent versions.

Delayed/scheduled messages wouldn't show up in the web console until their
scheduled time has arrived, so I don't think that's relevant to the
behavior you're seeing.

Tim

On Thu, Mar 22, 2018 at 5:28 AM, ajayvaghelanw 
wrote:

> Hello,
>
> I am using ActiveMQ 5.15.0 and there are multiple queues in system which
> helps to communicate my system for each queue there is an individual
> system.
>
> But, sometimes in a queue multiple messages of any random time period got
> stuck but after that time period newer messages is consumed but older
> remained in queue.
>
> I have added delay configuration in ActiveMQ. (Is it the reason??)
>
> I have tried to identify the cause but not come to any conclusion.
>
> I have seen that ActiveMQ has similar kind of problem in version older than
> 5.9.
>
>
> Please help me out.
>
> 
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>