Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <4CC6FB5E.5040507@tech4learning.com>
Date: Tue, 26 Oct 2010 11:01:34 -0500
From: Michael Brewer-Davis <michael@tech4learning.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US;
 rv:1.9.2.11) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5
MIME-Version: 1.0
To: users@activemq.apache.org
Subject: Re: Problem with simple peer-configuration, my config or AMQ issue?
References: <1288079610288-3013268.post@n4.nabble.com>
 <AANLkTinOcJJAn5BTdwwfZShYPZr8w=ULZCWbOeoEtwJx@mail.gmail.com>
In-Reply-To: <AANLkTinOcJJAn5BTdwwfZShYPZr8w=ULZCWbOeoEtwJx@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 10/26/2010 4:24 AM, Gary Tully wrote:
> That looks like a bug in the peer transport factory. I uses
> localhost:0 as the tcp transport url, but localhost maps to the
> loopback address since 5.3[1] so the connection is refused.
> The peer transport factory should use the wildcard address, 0.0.0.0

For me, the problem has been a little more complicated than this. 
Switching PeerTransportFactory to using 0.0.0.0 sends my message, but 
sends my non-DNS computer name as the target host, so the alive message is:

     %localhost%Michael-Dell:49225

If I comment out that section of TcpTransportServer, I can get 0.0.0.0 
instead of Michael-Dell, but that's not much more helpful.

If I commit to a network interface, I can get the discovery message to 
be useful, but I'm not aware of a "right" way to pick the network 
interface when several are available.

Is there a reason why the MulticastDiscoveryAgent doesn't consider the 
source IP of a discovery message?

michael

>
> Can you raise a jira issue for this? It is an easy fix, so we can get
> it quickly into a new snapshot.
>
> As a work around, you would need to use an xml configuration file for
> each broker and the xbean
> url scheme: http://activemq.apache.org/broker-xbean-uri.html
>
> [1] https://issues.apache.org/activemq/browse/AMQ-2094
>