Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0BD93F6F3 for ; Thu, 28 Mar 2013 15:36:49 +0000 (UTC) Received: (qmail 30091 invoked by uid 500); 28 Mar 2013 15:36:48 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 29952 invoked by uid 500); 28 Mar 2013 15:36:47 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 29923 invoked by uid 99); 28 Mar 2013 15:36:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Mar 2013 15:36:46 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of christian.posta@gmail.com designates 209.85.215.44 as permitted sender) Received: from [209.85.215.44] (HELO mail-la0-f44.google.com) (209.85.215.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Mar 2013 15:36:43 +0000 Received: by mail-la0-f44.google.com with SMTP id eb20so18076435lab.17 for ; Thu, 28 Mar 2013 08:36:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=BL90k3VPGy5Sj+8HF2bGUuJdNA6vd7qEspcHi+tOs2w=; b=Kjk6YnD5QvLXfXKb9E5WWqMXAQamLPR8xKulzwXqkjSVuKUF3uqfKgtWLey1qPaW6X FGC1N6YVVWXBScDbCpqmG+FXpFt+Qesh9baeb4AVfEklSeXETGfLROt6vGpkh2RadFte kXVWLkGqyKkUHUwmSBuZJ0frdg4cc4hg3fE7yCj42Ql4xLC2p0XWx1c7fzEjfySHjvj3 2YUHRn+UHDNnlt1xCcRtEyOvn8Prri2lKqgzXCqrTjb+T17jQ+Wh2swnH0lm5Qkp0QY6 NMSRQ8brGFo1QC7Q19M5d6HWvoORzFWGVzeYL4LbP5KxRRWfu3jmxGQsfms8y5NKCRfa /wvg== MIME-Version: 1.0 X-Received: by 10.112.79.1 with SMTP id f1mr12722186lbx.114.1364484981330; Thu, 28 Mar 2013 08:36:21 -0700 (PDT) Received: by 10.114.38.66 with HTTP; Thu, 28 Mar 2013 08:36:21 -0700 (PDT) In-Reply-To: <1364463985122-4665247.post@n4.nabble.com> References: <1364206479884-4665093.post@n4.nabble.com> <1364218303089-4665103.post@n4.nabble.com> <1364463985122-4665247.post@n4.nabble.com> Date: Thu, 28 Mar 2013 08:36:21 -0700 Message-ID: Subject: Re: AMQ_SCHEDULER_ACTION_BROWSE returns incomplete list From: Christian Posta To: "users@activemq.apache.org" Content-Type: multipart/alternative; boundary=90e6ba308e509d1d4f04d8fdeaac X-Virus-Checked: Checked by ClamAV on apache.org --90e6ba308e509d1d4f04d8fdeaac Content-Type: text/plain; charset=ISO-8859-1 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 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 --90e6ba308e509d1d4f04d8fdeaac--