Re: Not binding to localhost by default in jboss-head was: Re: [jboss-dev] Clustering bootstrap still taking a long time
Adrian wrote:
On Thu, 2007-11-08 at 09:22 -0600, Brian Stansberry wrote:
> Is your server bound to your VPN interface?
>
> > GMS: address is 10.11.14.31:32796
Ok, then that reveals a different problem.
If I add "-b localhost", I see:
16:28:10,188 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.1:32805
-------------------------------------------------------
16:28:12,523 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.1:32807
-------------------------------------------------------
...
16:28:37,115 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.Beta3
(build: SVNTag=JBoss_5_0_0_Beta3 date=200711081439)] Started in
1m:42s:463ms
Not great, but better! :-)
However, "-b localhost" should be the default!
Yeah, it's not. If you don't specify -b or otherwise specify how
JGroups binds, JGroups picks the first non-loopback interface.
The only issue here is how much we care about whether we can still say
"go to two nodes and './run.sh -c all' and you'll have a cluster".
TBH,
I don't much care about that any more and have no objections to having
the AS set a localhost default. Would be interested in opinions of
others though.
(BTW, clustering JBM requires assigning a unique server peer id to each
node, so "go to two nodes and './run.sh -c all' and you'll have a
cluster" doesn't work anymore anyway. JBM guys might find a solution to
that though.)
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com