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 5A61011C52 for ; Thu, 3 Jul 2014 09:53:41 +0000 (UTC) Received: (qmail 28558 invoked by uid 500); 3 Jul 2014 09:53:41 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 28509 invoked by uid 500); 3 Jul 2014 09:53:41 -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 28498 invoked by uid 99); 3 Jul 2014 09:53:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2014 09:53:40 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [195.47.198.139] (HELO mail02.uk.mizuho-sc.com) (195.47.198.139) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2014 09:53:38 +0000 From: Donnell Alwyn To: "'users@activemq.apache.org'" Subject: RE: Messages in queue but not consumed Thread-Topic: Messages in queue but not consumed Thread-Index: Ac+WlVh/gfKTG8ZhQW29y2h0rWR0egADtmRA Date: Thu, 3 Jul 2014 09:53:04 +0000 Message-ID: <5ED6BEB3153E1B419699EFD5571037E40FCB5D71@IPW-EXMBX01L.uk.mizuho-sc.com> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.110.125.19] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org I had a similar issue in ActiveMQ 5.7.=20 Messages stuck on the pending queue would never come off, new messages woul= d process ok. A broker restart was required to get messages off the pending= queue. Upgrading to 5.9 solved my problem. Regards Alwyn ------------------------------------------------------------------------ Alwyn Donnell ISD Middleware and Architecture Mizuho International Bracken House 1 Friday Street London EC4M 9JA email: alwyn.donnell@uk.mizuho-sc.com Tel.: +44 (0)20 7090 6569 -----Original Message----- From: Rahn Nicholas, Bedag [mailto:Nicholas.Rahn@bedag.ch]=20 Sent: 03 July 2014 10:27 To: 'users@activemq.apache.org' Subject: Messages in queue but not consumed We've noticed a problem in our production ActiveMQ 5.8 instances where mess= ages remain in a queue even when there are active consumers on that queue. = Most messages are consumed by the consumers, but a few do not and remain in= the queue. They just seem to be stuck there. Here's our setup: - 2 instances of ActiveMQ 5.8 in a failover (master/slave) setup on l= inux - JDBC (MSSQL) for the message store I've been able to reproduce this situation manually by doing the following: 1. Create 2 consumers on a queue. 2. Run 2 Producers (from 2 separate processes) simultaneously to send = 1000 messages each to the queue. 3. Use JMX to check the QueueSize of the queue. Not everytime, but every second or third run of the 2 simultaneous producer= s, not all of the 2000 messages will be consumed. When this happens, the c= onsumers are still running and idle, but the QueueSize is non-zero (can be = anything from 1 - 5, usually) and I can see the messages in the database. T= he unconsumed messages do not stop later messages from being consumed, howe= ver. A broker restart causes the 'stuck' messages to be immediately sent to= the consumers. It seems to have something to do with the multiple simultaneous producers a= s running just 1 producer at a time works as normal with all messages consu= med. I have tried to create a self-contained unit test (i.e. vm broker) for= this, but was not able to reproduce the situation. However, a unit test co= nnecting to a remote broker did show the same situation (with many more stu= ck messages). That would lead me to guess that the issue is perhaps in the = JDBC store code, but that's just a guess. Is this a known issue? Is there any workaround for it? Is it corrected in = a version later than 5.8? Thanks for the help. Nick This message and any files transmitted with it are confidential and intende= d solely for the use of the individual or entity to whom they are addressed= . If you have received this message in error please delete it and any files= transmitted with it, after notifying postmaster@uk.mizuho-sc.com. =20 Any opinions expressed in this message may be those of the author and not n= ecessarily those of the company. The company accepts no responsibility for = the accuracy or completeness of any information contained herein. This mess= age is not intended to create legal relations between the company and the r= ecipient.=20 Recipients should please note that messages sent via the Internet may be in= tercepted and that caution should therefore be exercised before dispatching= to the company any confidential or sensitive information.=20 Mizuho International plc Bracken House, One Friday Street, London EC4M 9JA.= TEL. 020 72361090. Wholly owned subsidiary of Mizuho Securities Co., Ltd. = Member of Mizuho Financial Group. Authorised by the Prudential Regulation A= uthority and regulated by the Financial Conduct Authority and the Prudentia= l Regulation Authority. Member of the London Stock Exchange. Registered in England No. 1203696. Registered office as above.