From users-return-11357-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Fri Nov 09 07:40:10 2007 Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 288 invoked from network); 9 Nov 2007 07:40:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Nov 2007 07:40:10 -0000 Received: (qmail 91840 invoked by uid 500); 9 Nov 2007 07:39:57 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 91813 invoked by uid 500); 9 Nov 2007 07:39:56 -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 91804 invoked by uid 99); 9 Nov 2007 07:39:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2007 23:39:56 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG 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; Fri, 09 Nov 2007 07:40:36 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1IqOSo-0004mS-A9 for users@activemq.apache.org; Thu, 08 Nov 2007 23:39:38 -0800 Message-ID: <13662640.post@talk.nabble.com> Date: Thu, 8 Nov 2007 23:39:38 -0800 (PST) From: hbruch To: users@activemq.apache.org Subject: NetworkTTL filters AdvisoryMessages only after transmission MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: holger.bruch@isb-ag.de X-Virus-Checked: Checked by ClamAV on apache.org Hi, we are using a star topology, having multiple 4.0.2-brokers connected to one central broker via a slow, unreliable network. Network connectors are configured with a networkTTL=1. However, AdvisoryMessages are sent over two hops before they get discarded: 2007-11-09 07:35:13,733 DEBUG DemandForwardingBridge - Ignoring Subscription ConsumerInfo {commandId = 3, responseRequired = false, consumerId = ID:xxx-4397-1194590104420-5:1:1:1, destination = queue://TEST.FOO, prefetchSize = 1, maximumPendingMessageLimit = 0, browser = false, dispatchAsync = false, selector = null, subcriptionName = null, noLocal = false, exclusive = false, retroactive = false, priority = 0, brokerPath = [ID:xxx-4397-1194590104420-2:1], optimizedAcknowledge = false, noRangeAcks = false, additionalPredicate = org.apache.activemq.command.NetworkBridgeFilter@61a907} restricted to 1 network hops only Is there a way to restrict advisory messages to only one hop? The network connector is configured to use the DemandForwardingBridge (conduitSubscriptions=false): It seems to me, that TopicSubscriptions from remote brokers don't have NetworkBridgeFilter set as additionalPredicate. Is this correct? Currently we encounter many irrelevant advisory messages filling up memory pretty fast since connections are unreliable and therefore consumers connect/disconnect regularly. As a result, the UsageManager.waitForSpace() steps in soon and halts the producer. Any help is appreciated, thanks, Holger -- View this message in context: http://www.nabble.com/NetworkTTL-filters-AdvisoryMessages-only-after-transmission-tf4776251s2354.html#a13662640 Sent from the ActiveMQ - User mailing list archive at Nabble.com.