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: http://svn.apache.org/viewvc/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/broker/scheduler/JobSchedulerManagementTest.java?view=markup On Thu, Mar 28, 2013 at 2:46 AM, jliezers <john.liez...@metoffice.gov.uk>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: > http://activemq.2283324.n4.nabble.com/AMQ-SCHEDULER-ACTION-BROWSE-returns-incomplete-list-tp4665093p4665247.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
