Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 81857 invoked from network); 31 Mar 2009 15:49:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 31 Mar 2009 15:49:25 -0000 Received: (qmail 87486 invoked by uid 500); 31 Mar 2009 15:49:24 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 87459 invoked by uid 500); 31 Mar 2009 15:49:24 -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 87449 invoked by uid 99); 31 Mar 2009 15:49:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Mar 2009 15:49:24 +0000 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 (athena.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; Tue, 31 Mar 2009 15:49:16 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LogCu-0001Vs-4a for users@activemq.apache.org; Tue, 31 Mar 2009 08:48:56 -0700 Message-ID: <22805036.post@talk.nabble.com> Date: Tue, 31 Mar 2009 08:48:56 -0700 (PDT) From: andymorris To: users@activemq.apache.org Subject: Re: Messages getting Stuck In-Reply-To: <22804687.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: andymorris81@gmail.com References: <19437217.post@talk.nabble.com> <73394860-BA27-49B1-AFEB-A514B37E6664@gmail.com> <19449362.post@talk.nabble.com> <19489877.post@talk.nabble.com> <22803094.post@talk.nabble.com> <22804687.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Oh that's a shame. Have been trying OpenMQ but had some probs (namely http://forums.sun.com/thread.jspa?threadID=5377354&tstart=0) but I really can't believe there isn't a workaround for this - ActiveMQ is held in quite a high regard and is used quite a lot of commercial environments. Hmm, thanks for your reply, has anyone else experienced this (and hopefully solved it!)? krv wrote: > > Hi Andy, > > Even after doing some research and tries I didn't succeed in my original > problem which is when I started looking for alternate solutions. OpenMQ > seem to suite our needs and helped us overcome this particular problem. > So, we went ahead with OpenMQ. > > But not sure if OpenMQ offers the features that you require. You can check > out its features and give it a try if it suits you. > > Again here, no offence to ActiveMQ users. > > Regards, > Vivek > > andymorris wrote: >> >> Hi guys/gals >> >> I know this is a fairly old post but I am experiencing exactly the same >> problem as described using version 5.2, so any bug may not have been >> fixed. >> >> After failover a load of messages (have seen up to 7000) get stuck, if I >> then restart the dead node and kill the new master (so switching back) >> then some of the messages get consumed, however this is only a few >> hundred or thousand and it gets stuck again. I keep switching broker node >> by restarting the dead one and killing the master and it tends to get >> through the remainding messages, but it tends to get to a few hundred >> left and no more restarting helps. >> >> My setup is: >> ActiveMQ 5.2 HA with two nodes master and slave. >> Java 6 >> Spring 2.5 >> Jencks to provide pooled connections (inbound and outbound) >> JmsTemplate >> Running from jar file (no appserver in this environment) >> >> FYI our company has used ActiveMQ for the last few years and has had >> quite a few problems (some their fault like putting 50mb files in >> messages!) and I'm meant to be looking at alternatives. I'd like to prove >> that if we use it properly and upgrade to the latest version that there'd >> be no/less significant problems. >> >> Any help would be greatly appreciated. >> >> andy >> >> >> rajdavies wrote: >>> >>> Hi Vivek, >>> >>> do you get the same behaviour with the default store (AMQ) ? You can >>> set this by commenting out the persistence option from your >>> configuration >>> >>> cheers, >>> >>> Rob >>> On 15 Sep 2008, at 10:40, krv wrote: >>> >>>> >>>> Ok, now I tried the latest version (5.2.0-SNAPSHOT) and faced the >>>> issue at a >>>> very early stage. Also the GUI was not showing number of messages >>>> enqueued/dequeued properly. The counts were wrong. >>>> >>>> Please post if you have got any relevant information. >>>> >>>> Thanks in advance. >>>> >>>> Regards, >>>> Vivek >>>> >>>> >>>> krv wrote: >>>>> >>>>> Hi Rob, >>>>> >>>>> Thanks for the advice. I tried using 5.1.0 but the issue was still >>>>> there. >>>>> I hope my configuration is correct - >>>>> http://www.nabble.com/file/p19449362/activemq.xml activemq.xml and >>>>> did >>>>> not miss any configuration. >>>>> >>>>> Please let me know if you get anything. I'll also be trying the >>>>> latest >>>>> SNAPSHOT, but I don't think I can wait for long for the stable >>>>> version. >>>>> >>>>> Regards, >>>>> Vivek >>>>> >>>>> >>>>> rajdavies wrote: >>>>>> >>>>>> Hi Vivek, >>>>>> >>>>>> this could well be a known bug - can you use 5.1 - or 5.2 (due out >>>>>> soon) >>>>>> >>>>>> thanks, >>>>>> >>>>>> Rob >>>>>> On 11 Sep 2008, at 16:31, krv wrote: >>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Sorry for posting this again, but I did not find any solution to >>>>>>> the >>>>>>> problem >>>>>>> in the threads posted for the similar problem. >>>>>>> >>>>>>> I'm using using ActiveMQ 5.0.0. I have a single enqueuer which >>>>>>> enqueues say >>>>>>> about 100 messages for a request. I have multiple (threaded) >>>>>>> dequeuers >>>>>>> running on different machines which poll Amq for messages. >>>>>>> >>>>>>> After about 2k-3k messages (or probably time) I see messages >>>>>>> getting >>>>>>> stuck >>>>>>> in the AMQ store (I'm using pure JDBC persistence using mysql). I >>>>>>> can see >>>>>>> the messages in the DB but the consumers do not get it. If I >>>>>>> restart >>>>>>> ActiveMQ the messages are delivered. I've attached my file - >>>>>>> http://www.nabble.com/file/p19437217/activemq.xml activemq.xml . >>>>>>> >>>>>>> Any kind of help is greatly appreciated. >>>>>>> >>>>>>> Regards, >>>>>>> Vivek >>>>>>> -- >>>>>>> View this message in context: >>>>>>> http://www.nabble.com/Messages-getting-Stuck-tp19437217p19437217.html >>>>>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/Messages-getting-Stuck-tp19437217p19489877.html >>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >>>> >>> >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/Messages-getting-Stuck-tp19437217p22805036.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.