Return-Path: 
 <activemq-users-return-6427-apmail-geronimo-activemq-users-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org
Received: (qmail 71276 invoked from network); 1 Jan 2007 05:10:57 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 1 Jan 2007 05:10:57 -0000
Received: (qmail 24406 invoked by uid 500); 1 Jan 2007 05:11:04 -0000
Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org
Received: (qmail 24390 invoked by uid 500); 1 Jan 2007 05:11:03 -0000
Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:activemq-users-help@geronimo.apache.org>
List-Unsubscribe: <mailto:activemq-users-unsubscribe@geronimo.apache.org>
List-Post: <mailto:activemq-users@geronimo.apache.org>
List-Id: <activemq-users.geronimo.apache.org>
Reply-To: activemq-users@geronimo.apache.org
Delivered-To: mailing list activemq-users@geronimo.apache.org
Received: (qmail 24381 invoked by uid 99); 1 Jan 2007 05:11:03 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 31 Dec 2006 21:11:03 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 31 Dec 2006 21:10:53 -0800
Received: from [72.21.53.38] (helo=jubjub.nabble.com)
	by talk.nabble.com with esmtp (Exim 4.50)
	id 1H1FRQ-0000nR-K1
	for activemq-users@geronimo.apache.org; Sun, 31 Dec 2006 21:10:32 -0800
Message-ID: <8111975.post@talk.nabble.com>
Date: Sun, 31 Dec 2006 21:10:32 -0800 (PST)
From: frankr <frank@aqon.com>
To: activemq-users@geronimo.apache.org
Subject: Network Connector over unreliable WAN connection
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: frank@aqon.com
X-Virus-Checked: Checked by ClamAV on apache.org


I'm trying to setup a network connector between 2 brokers over an unreliable
WAN connection (the internet). The first batch of messages (immediately
after startup) are sent over just fine, however the second batch (after a
short idle time) is never send. My connector configuration is as follows:

<networkConnector uri="static:(tcp://10.10.10.10:61616)"
	failover="false"
	name="conn1"
	dynamicOnly="true"
	conduitSubscriptions="false"
	decreaseNetworkConsumerPriority="false" >
		<dynamicallyIncludedDestinations>
			<queue physicalName="myapp/queue/inbound1"/>
		</dynamicallyIncludedDestinations>
</networkConnector>

I have a producer generating messages on the first broker and a consumer on
the second broker.

I tried this configuration and other variations on parameter settings
without avail. Tested both on v4.0.2 and 4.1.0 as well as 4.1.0 patched
according to AMQ-961, all without success.

I'm sure that I miss something in the configuration, however I am not able
to figure this one out.

How can I make the static network connector more resilient to network
hick-ups? Any input appreciated.

-- 
View this message in context: http://www.nabble.com/Network-Connector-over-unreliable-WAN-connection-tf2903424.html#a8111975
Sent from the ActiveMQ - User mailing list archive at Nabble.com.