Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 66245 invoked from network); 10 Feb 2008 09:10:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Feb 2008 09:10:20 -0000 Received: (qmail 62831 invoked by uid 500); 10 Feb 2008 09:10:13 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 62804 invoked by uid 500); 10 Feb 2008 09:10:13 -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 62794 invoked by uid 99); 10 Feb 2008 09:10:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Feb 2008 01:10:13 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Feb 2008 09:09:27 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1JO8C3-0005kZ-Ui for users@activemq.apache.org; Sun, 10 Feb 2008 01:09:47 -0800 Message-ID: <15394557.post@talk.nabble.com> Date: Sun, 10 Feb 2008 01:09:47 -0800 (PST) From: Jason Rosenberg To: users@activemq.apache.org Subject: Re: Sent + Pending should equal Received, no? In-Reply-To: <15370321.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: jrosenberg@shopzilla.com References: <15367886.post@talk.nabble.com> <15370200.post@talk.nabble.com> <15370321.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Ok, I enabled DEBUG logging on the broker, and now I see this on restart: 2008-02-10 03:52:43,645 [127.0.0.1:64511] DEBUG RecoveryListenerAdapter - Message id ID:szjrosenberg-mbp17.local-64382-1202633445267-0:22:1:1:1 could not be recovered from the data store - already dispatched In fact, I see 8 of these, and the webconsole in this case now shows '8' pending messages for the queue, but never delivers them. The webconsole showed 0 pending messages before shutting down, etc... I guess there are 2 issues. First, if it can't recover the message, it probably shouldn't show it as pending. Second, need to find out why it's even trying to recover the message in the first place, after showing no Pending message before shutdown. I'm using a 5.1-SNAPSHOT broker that I downloaded around Jan 24, 2008.... Jason Jason Rosenberg wrote: > > Now, after closing down all connected clients, and restarting the broker, > the webconsole shows the same queue has 2 pending messages....Clicking on > browse messages shows no messages..... > > I'm wondering if the jmx QueueViewMBean needs to have more refinement to > display more detailed status of messages that are in various states (e.g. > cached, redelivered, recovered, rolled-back, etc.)... > > Or is it likely a bug altogether... > > Fun stuff > > Jason > > > > Jason Rosenberg wrote: >> >> I just tried clicking on "purge" in the webconsole, on a queue that >> seemed to have messages stuck in the pending state. After the purge, it >> now shows that it has -4 messges pending. >> >> Should it ever be a negative number of messages pending? >> >> Jason >> >> >> >> >> Jason Rosenberg wrote: >>> >>> I have a scenario, with amq 5.1.... >>> >>> Where more messages are being received than are sent. Should that be >>> possible? It looks like indeed some of the messages are getting >>> delivered twice, and tallied as such in the webconsole view of the >>> queue....Is there some setting I need to place on my queues to make sure >>> this doesn't happen? Or is it a bug... >>> >>> I'm using the amqPersistence for persistent messaging. >>> >>> Also, see my previous post, regarding the broker showing new messages >>> Pending after restarting the broker.... >>> >>> Weirdness, it would seem.... >>> >>> The config is very much the same as what I had previously with 4.1.1, >>> using the default persistence there (journaled file-based jdbc).... >>> >>> Jason >>> >> >> > > -- View this message in context: http://www.nabble.com/Sent-%2B-Pending-should-equal-Received%2C-no--tp15367886s2354p15394557.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.