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 395D5E057 for ; Wed, 13 Feb 2013 16:05:41 +0000 (UTC) Received: (qmail 33617 invoked by uid 500); 13 Feb 2013 16:05:40 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 33591 invoked by uid 500); 13 Feb 2013 16:05: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 33552 invoked by uid 99); 13 Feb 2013 16:05:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Feb 2013 16:05:38 +0000 X-ASF-Spam-Status: No, hits=3.5 required=5.0 tests=HTML_MESSAGE,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of suonayi2006@163.com designates 220.181.13.80 as permitted sender) Received: from [220.181.13.80] (HELO m13-80.163.com) (220.181.13.80) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Feb 2013 16:05:32 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Received:Date:From:To:Subject:In-Reply-To: References:Content-Type:MIME-Version:Message-ID; bh=+gfKtAD4dYrw rLQp9e/XUlj/U+QTtyZjtRLOZSCy6Rg=; b=Ew0p4WpVsrHB6GyA/qHPTTAIsfF6 o5i66MsELhQv+UFzEcrmN8Fi7Lcn/1FM5anPpfv458uSLQJm7cPaVxKqe3sNlulB B86P3QyDuYbFnhrDXpL4MyBQPk/Mox3MSzALUOxyPdMSk5QjEML3gVjzlz8HVPsZ OUafJ8Jjkc52njM= Received: from suonayi2006$163.com ( [114.249.245.124] ) by ajax-webmail-wmsvr80 (Coremail) ; Thu, 14 Feb 2013 00:05:07 +0800 (CST) X-Originating-IP: [114.249.245.124] Date: Thu, 14 Feb 2013 00:05:07 +0800 (CST) From: SuoNayi To: users@activemq.apache.org Subject: Re:Re: Successfully delivered message ends up on DLQ X-Priority: 3 X-Mailer: Coremail Webmail Server Version SP_ntes V3.5 build 20130124(21453.5226.5222) Copyright (c) 2002-2013 www.mailtech.cn 163com In-Reply-To: <1360753264128-4663321.post@n4.nabble.com> References: <1360664426648-4663232.post@n4.nabble.com> <1360742141663-4663319.post@n4.nabble.com> <1360744699241-4663320.post@n4.nabble.com> <1360753264128-4663321.post@n4.nabble.com> X-CM-CTRLDATA: uHyaz2Zvb3Rlcl9odG09MTYwNDo4MQ== Content-Type: multipart/alternative; boundary="----=_Part_36166_131672454.1360771507087" MIME-Version: 1.0 Message-ID: <2de4bb05.2618.13cd44d638f.Coremail.suonayi2006@163.com> X-CM-TRANSID: UMGowEA5rUCzuRtRdstMAA--.21860W X-CM-SenderInfo: xvxr0td1lsiiqw6rljoofrz/1tbiFgbCGlEABGE4TgAAsK X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU== X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_36166_131672454.1360771507087 Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: 7bit Just want to know the root cause about this and after digging the source code I find even if a message ack is processed unsuccessfully by broker the consumer will not know that.So I'm very strange about your experience.Is the message in the dlq redelivered? you can see the properties of the message in the dql via web console. Do you change the default redelivery policy? At 2013-02-13 19:01:04,jliezers wrote: >I now believe the root cause is an our enthusiastic slave activemq consuming >sessions attempting to acquire the lock on the ACTIVEMQ_LOCK table. We have >a large number (100+) of unexpected sessions issuing UPDATE LOCK queries and >then waiting. These are probably triggering the underlying connection resets >as the max active sessions is only set to 200. > > > >-- >View this message in context: http://activemq.2283324.n4.nabble.com/Successfully-delivered-message-ends-up-on-DLQ-tp4663232p4663321.html >Sent from the ActiveMQ - User mailing list archive at Nabble.com. ------=_Part_36166_131672454.1360771507087--