Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 31742 invoked from network); 31 Jan 2009 00:02:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Jan 2009 00:02:41 -0000 Received: (qmail 40856 invoked by uid 500); 31 Jan 2009 00:02:40 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 40833 invoked by uid 500); 31 Jan 2009 00:02:40 -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 40822 invoked by uid 99); 31 Jan 2009 00:02:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Jan 2009 16:02:40 -0800 X-ASF-Spam-Status: No, hits=2.4 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of e.semog@gmail.com designates 74.125.44.153 as permitted sender) Received: from [74.125.44.153] (HELO yx-out-1718.google.com) (74.125.44.153) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 31 Jan 2009 00:02:30 +0000 Received: by yx-out-1718.google.com with SMTP id 3so263142yxi.86 for ; Fri, 30 Jan 2009 16:02:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=IHAbTiro7GcXePhNfLQVMqtVv3RUc03tx/J/HjTTTnk=; b=Y00N/IlQLjWYWQegJEWXI8KWjCWRq8sfpvVoYpwgSQBMu7zTgs30v0fVqW7gTA6egr M+tLHUuJmgT3kFSg2fPvPSatmVKlhIIqQeN3ZuMqPEad0IZEIkXRUDcpJIbUkgZuiveD cq8ZAx6Bj+H/QyQV5SJjKfhmHahUYFHTRAupk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=VPbaHtdenvDJfSkAW5PP3cnBGY7CT9taXDYXsxRbo5FMj3JlQic7zunxLzmUL9iS+e yL0EgVaO3cat/K1k4F3C7jeGbxZNjnkneLAqOIscmvIG/Yx+8qm/ijRved0J8PqLVF5t /4aeW21lKBvjH7aJI8mA+Q9w/X91xsoI96y6A= MIME-Version: 1.0 Received: by 10.90.106.4 with SMTP id e4mr1426514agc.76.1233360129390; Fri, 30 Jan 2009 16:02:09 -0800 (PST) In-Reply-To: <21443338.post@talk.nabble.com> References: <21438163.post@talk.nabble.com> <3a73c17c0901130843i2229726cu4db026557e57a42c@mail.gmail.com> <21440240.post@talk.nabble.com> <3a73c17c0901131024x4add14b5v220dd60ed2cb64d3@mail.gmail.com> <21442857.post@talk.nabble.com> <7b3355cb0901131143p777046ecte017761cb4bcc794@mail.gmail.com> <21443338.post@talk.nabble.com> Date: Fri, 30 Jan 2009 16:02:09 -0800 Message-ID: <5a56ce1b0901301602o553c4b96k72455fa2034287e4@mail.gmail.com> Subject: Re: Q Consumers stop receiving messages From: Jim Gomes To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=0016e644cf326479ad0461bc0831 X-Virus-Checked: Checked by ClamAV on apache.org --0016e644cf326479ad0461bc0831 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Any updates on this issue? This seems very similar to a problem we are experiencing with the broker halting dispatch of messages to consumers that are ready and able to receive messages. Our problem definitely seems to be surrounding the flagging of messages as persistent. Our current work-around is we installed a plug-in that turns off the persistent flag before the message is inserted into the broker destinations. This allowed us to avoid any client-side code/logic changes. Once we forced all messages to turn off the persistent flag, then all of our messages are flowing without any hiccups. I am very suspect of the code logic inside ActiveMQ that handles persistent message routing and delivery. This is with the shipping 5.1.0, 5.2.0, and previous 5.3-SNAPSHOT versions. I haven't updated 5.3 in about a month, so I can't speak to the very latest version. - Jim On Tue, Jan 13, 2009 at 12:02 PM, IBeaumont wrote: > > The application is already written, and currently we use either MQSeries or > SwiftMQ for the queue provider. I tried to drop ActiveMQ in a few years > back but the performance was awful. With version 5 it seems the > performance > problems are sorted. Implementing a MessageListener isn't an ideal > solution > as I'd need to change a lot of other code. I'm trying to avoid any > changes. > > > > bsnyder wrote: > > > > On Tue, Jan 13, 2009 at 12:35 PM, IBeaumont > > wrote: > >> > >> I'm sending a mixture of persistent and non persistent messages. > >> > >> I have seen a negative queue count before so will look at the trunk. > >> > >> Can't see anything unusal in JConsole, but I have just downlaoded the > >> source > >> and in the ActiveMQMessageConsumer.receiveNoWait there are these > lines... > >> if (info.getPrefetchSize() == 0) { > >> md = dequeue(-1); // We let the broker let us know when we > >> // timeout. > >> } else { > >> md = dequeue(0); > >> } > >> > >> So that explains why my consumes seem to hang when things go wrong - > >> because > >> they wait forever because I have a prefetchSize of zero. > >> > >> I've now changed me code so that instead of using receiveNoWait, I'll > use > >> "receive" with a short timeout. Hopefully then things will timeout and > >> messages will contiue to be processed. I'll then need to find out if > all > >> any messages get skipped. ALthough that doesn't help find the cause. > > > > I'm just curious, instead of using the synchronous methods have you > > considered using the asynchronous API by implementing a > > MessageListener? > > > > Bruce > > -- > > perl -e 'print > > unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E > );' > > > > Apache ActiveMQ - http://activemq.org/ > > Apache Camel - http://activemq.org/camel/ > > Apache ServiceMix - http://servicemix.org/ > > > > Blog: http://bruceblog.org/ > > > > > > -- > View this message in context: > http://www.nabble.com/Q-Consumers-stop-receiving-messages-tp21438163p21443338.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > --0016e644cf326479ad0461bc0831--