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 327107ECF for ; Mon, 5 Dec 2011 19:48:44 +0000 (UTC) Received: (qmail 76518 invoked by uid 500); 5 Dec 2011 19:48:43 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 76496 invoked by uid 500); 5 Dec 2011 19:48:43 -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 76488 invoked by uid 99); 5 Dec 2011 19:48:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Dec 2011 19:48:43 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=FREEMAIL_FROM,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 216.139.236.26 is neither permitted nor denied by domain of romanhawk@gmail.com) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Dec 2011 19:48:38 +0000 Received: from joe.nabble.com ([192.168.236.139]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1RXeWQ-0006d3-02 for users@activemq.apache.org; Mon, 05 Dec 2011 11:48:18 -0800 Date: Mon, 5 Dec 2011 11:48:17 -0800 (PST) From: romanhawk To: users@activemq.apache.org Message-ID: <1323114497988-4161875.post@n4.nabble.com> Subject: Proper handling of disconnected consumers - best approach MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Dear colleagues, I have the following scenario to implement and looking for best ways to accomplish it: 1. I have embedded broker on the server 2. There are several consumers running behind firewalls/NAT connected to that server 3. Messages are produced by the server and put into the embedded broker to be consumed by remote consumers 4. Communication is based on Queues so only one consumer should receive and handle the message There are messages, which can be processed by any consumer (some kind of clustering). If some consumer is gracefully turned off, messages are sent to remained consumers without any issue. But what if cable is simply unplugged and consumer is not reachable anymore. Still, as far as I understand, broker put the messages to be consumed by that "dead" consumer so eventually they would not be processed and end up in DLQ. Of course, after timeout, consumer will become disconnected as ActiveMQ will be aware of broken transport, but remaining messages would not be delivered to other consumers. What is the best approach to deal with such situation (messages put to "dead" consumer to be handled by another consumer). Message redelivery? Probably there is some simpler approach and I'm simply missing some XML configuration for such stuff. Though, as my broker is embedded, I can create any "hooks" to provide necessary functionality if necessary. -- View this message in context: http://activemq.2283324.n4.nabble.com/Proper-handling-of-disconnected-consumers-best-approach-tp4161875p4161875.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.