Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 96331 invoked from network); 1 Apr 2009 15:02:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Apr 2009 15:02:58 -0000 Received: (qmail 28299 invoked by uid 500); 1 Apr 2009 15:02:58 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 28258 invoked by uid 500); 1 Apr 2009 15:02:58 -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 28248 invoked by uid 99); 1 Apr 2009 15:02:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 15:02:58 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of MGottschalk@gmx.net designates 213.165.64.20 as permitted sender) Received: from [213.165.64.20] (HELO mail.gmx.net) (213.165.64.20) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 01 Apr 2009 15:02:50 +0000 Received: (qmail invoked by alias); 01 Apr 2009 15:02:27 -0000 Received: from unknown (EHLO fentanyl.toxine.lan) [195.180.2.195] by mail.gmx.net (mp036) with SMTP; 01 Apr 2009 17:02:27 +0200 X-Authenticated: #916294 X-Provags-ID: V01U2FsdGVkX1+A4N4f/keAKLMwMMEV/mNxZJ3sHAViaIAIPjoff6 mkmb2ytbciukAg From: Michael Gottschalk To: users@activemq.apache.org Subject: Re: Messages getting Stuck Date: Wed, 1 Apr 2009 17:02:28 +0200 User-Agent: KMail/1.9.10 References: <19437217.post@talk.nabble.com> <22804687.post@talk.nabble.com> <22805036.post@talk.nabble.com> In-Reply-To: <22805036.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200904011702.28773.MGottschalk@gmx.net> X-Y-GMX-Trusted: 0 X-FuHaFi: 0.51 X-Virus-Checked: Checked by ClamAV on apache.org Hi Andy, we also had similar problems with ActiveMQ 5.2 (see AMQ-2161). This is apparently fixed in fuse 5.3.0.0, so we switched to fuse. However, even with fuse, we had some additional problems, which we had to=20 patch ourselves (namely an out-of-memory problem and a problem with=20 interruptions). Our patches are available in the activemq JIRA (AMQ-2178 an= d=20 AMQ-2191). We still have one other problem (it occurred in activemq 5.2 and=20 5.3.0.0-fuse): the camel processors were very slow in some cases when using= =20 JMS transactions and they just stopped polling messages when using XA=20 transactions in some cases. We could only fix that problem by replacing all camel processors by custom= =20 code that implements routing and polling directly with Spring JmsTemplates. Cheers, Michael Am Dienstag 31 M=E4rz 2009 17:48:56 schrieb andymorris: > Oh that's a shame. Have been trying OpenMQ but had some probs (namely > http://forums.sun.com/thread.jspa?threadID=3D5377354&tstart=3D0) but I re= ally > can't believe there isn't a workaround for this - ActiveMQ is held in qui= te > a high regard and is used quite a lot of commercial environments. > > Hmm, thanks for your reply, has anyone else experienced this (and hopeful= ly > 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 > [...]