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 E1F4C88FF for ; Mon, 22 Aug 2011 15:02:08 +0000 (UTC) Received: (qmail 29874 invoked by uid 500); 22 Aug 2011 15:02:08 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 29795 invoked by uid 500); 22 Aug 2011 15:02:07 -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 29731 invoked by uid 99); 22 Aug 2011 15:02:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Aug 2011 15:02:07 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of ozan.seymen@tdpg.com does not designate 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Aug 2011 15:02:00 +0000 Received: from joe.nabble.com ([192.168.236.139]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QvW0R-0006hB-6C for users@activemq.apache.org; Mon, 22 Aug 2011 08:01:39 -0700 Date: Mon, 22 Aug 2011 08:01:39 -0700 (PDT) From: oseymen To: users@activemq.apache.org Message-ID: <1314025299182-3760397.post@n4.nabble.com> In-Reply-To: References: <1307720064197-3588714.post@n4.nabble.com> <1307815529968-3590852.post@n4.nabble.com> <1308228330231-3602343.post@n4.nabble.com> <1310546315706-3664510.post@n4.nabble.com> Subject: Re: Message loss in network of brokers - transactional send MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org >> "Also, I think a send transaction would help, it should encompass all of the composite destinations." That is correct. When I send messages in transaction, I get no message loss - but both JMX and admin console pending message count displays wrong number. My setup is still same - 2 brokers, connected with network of brokers. (Just to remind you:) Messages are flowing from broker1 to broker2. On broker2, I have configured the replicated queue as a composite queue so that I can divert incoming messages into multiple queues in broker2. When I send 3000 messages to broker1 (in transaction) and start killing brokers one by one randomly while messages are flowing, I end up having 3001 or 3002 pending messages count. When I execute a consumer on broker2, I can consume 3000 messages which is perfect. But admin console reports there is 1 message pending. When I browse the messages in the queue using admin console, it displays no messages. So even though there are no messages pending, somehow, JMX and admin console thinks that there is 1 message pending. When I restart broker2, pending messages count corrects itself and reports 0 in admin console. Have you ever encountered this problem before? Number of pending messages counter is very important for me for monitoring purposes. If it says 1 message is pending even though its not, I will get monitoring nightmares. I'd really appreciate any help or information. Cheers, Ozan -- View this message in context: http://activemq.2283324.n4.nabble.com/Message-loss-in-network-of-brokers-transactional-send-tp3588714p3760397.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.