Re: [jgroups-dev] External address/bind address question

Added your comment to the case.

Yes, this would be an alternative, but it would require external_addr to 
be set.

I could assign defaults to external_addr, similar to what's done with 
bind_addr. This would be resolved at stack initialization time.

Currently, external_addr is on BasicTCP. This would have to be changed, 
and it would have to be moved up in the hierarchy into TP.

I'll see whether this is feasible when I tackle the issue. I think this 
can be done in 2.12


On 1/4/11 10:18 PM, Jayesh Seshadri wrote:
> What would be the address visible to other entities (i.e. where would
> they send their packets to)?
> Note that currently if you use the external address 'override' for
> that, jgroups resolves the external_addr property using
> InetAddress.getByName on the node that the external_addr was assigned
> to, prior to advertising that address to the peers.
>
> A simple fix would be to skip that resolution on the node that the
> external_addr is assigned and simply advertise the supplied
> external_addr string as-is to the other nodes, requiring that to be
> resolvable from the other nodes. So if I set external_addr =
> 'foobar.corp.com', peers would get the peer address as
> "foobar.corp.com", and attempt to send packets to "foobar.corp.com",
> instead of the single IP returned by InetAddress.getByName().

-- 
Bela Ban
Lead JGroups / Clustering Team
JBoss

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Javagroups-development mailing list