Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 41586 invoked from network); 26 May 2010 08:50:10 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 May 2010 08:50:10 -0000 Received: (qmail 98561 invoked by uid 500); 26 May 2010 08:50:10 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 98518 invoked by uid 500); 26 May 2010 08:50:08 -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 98510 invoked by uid 99); 26 May 2010 08:50:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 May 2010 08:50:07 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 May 2010 08:50:01 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1OHCJ2-0005tc-EN for users@activemq.apache.org; Wed, 26 May 2010 01:49:40 -0700 Message-ID: <28678019.post@talk.nabble.com> Date: Wed, 26 May 2010 01:49:40 -0700 (PDT) From: gondor771 To: users@activemq.apache.org Subject: Forwarding bridge - connect at need feature ? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: tom@mips.com.hr X-Virus-Checked: Checked by ClamAV on apache.org Hi, I am using "forwarding bridge" in many-to-one configuration. Many ActiveMQ clients (just plain ActiveMQ local server acting as a buffer) will be forwarding several queues defined with staticallyIncludedDestinations to central (remote) ActiveMQ. So far, experiments confirm that all is working fine. However there is one problem with forwarding bridge - it keeps TCP/IP connection all the time. As there could be really many ActiveMQ clients => that will kill network router with overload of active TCP/IP connections. Most of these ActiveMQ clients will be idle 99% of the time (no data in queues to forward). Is there a way to configure client ActiveMQ in forwarding bridge mode to connect to remote server ONLY when there is something to be sent (and disconnect when done, eg queue empty) ? Can that be done by configuration or the only option is coding an application ? PS. Google did not help me on this one.:-( Tom -- View this message in context: http://old.nabble.com/Forwarding-bridge---connect-at-need-feature---tp28678019p28678019.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.