activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <>
Subject Re: AMQ_SCHEDULER_ACTION_BROWSE returns incomplete list
Date Thu, 28 Mar 2013 15:42:50 GMT
On 03/28/2013 11:36 AM, Christian Posta wrote:
> Yah, unless Tim or Gary know off hand why this is, I would say open a JIRA.
> I am not seeing any logic in the code that would filter out messages for a
> browse based on TTL.
> It would be great if you could throw together a little unit test that shows
> this and I can take a closer look. Take a look at this test for an example
> of a unit test:
A test case would be good.

The TTL should only be applied for the Message once its scheduled send 
time arrives such that the newly sent scheduled message will time out 
like any other message.  Scheduled tasks should "time out" based on 
their own scheduling criteria and not the TTL of the Message.
> On Thu, Mar 28, 2013 at 2:46 AM, jliezers <>wrote:
>> I can confirm that the deafult 3 hour expiration (timeToLive) value applied
>> to all messages by my template was causing the problem.
>> If I override and set expiration = 0 for the scheduled messages then they
>> are browsable.
>> Is there a JIRA required here?
>> Should ActiveMQ schedule browse action disregard expiration and not filter
>> out expired messages when browsing the scheduled message list?
>> Should scheduled messages always have expiration set to zero?
>> --
>> View this message in context:
>> Sent from the ActiveMQ - User mailing list archive at

Tim Bish
Sr Software Engineer | RedHat Inc. | |
skype: tabish121 | twitter: @tabish121

View raw message