Problems starting AutomaticDiscovery on Mac OSX 10.3

[ricsearle]

Hello,

I'm trying to get JBOSS 3.2.3 running on a Mac OSX 10.3 laptop. We have in running in production on a large number of OSX Server boxes, so I'm happy that the platform should work.

When I start it on my Powerbook however, I get:

2004-03-25 10:08:42,501 INFO [org.jboss.ha.jndi.HANamingService] Listening on /0.0.0.0:1100
2004-03-25 10:08:42,527 WARN [org.jboss.ha.jndi.HANamingService] Failed to start AutomaticDiscovery
java.net.SocketException: bad argument for IP_MULTICAST_IF: address not bound to any interface
 at java.net.PlainDatagramSocketImpl.socketSetOption(Native Method)
 at java.net.PlainDatagramSocketImpl.setOption(PlainDatagramSocketImpl.java:260)
 at java.net.MulticastSocket.setInterface(MulticastSocket.java:418)
 at org.jboss.ha.jndi.HANamingService$AutomaticDiscovery.start(HANamingService.java:476)
 at org.jboss.ha.jndi.HANamingService.startService(HANamingService.java:261)
...

The cluster-service.xml hasn't been modified from the 'all' config.

I've tried everything I can think of, including adding static routes for the multicast addresses, but I can't make this error go away.

Any help would be greatly appreciated!

Regards,

Ric Searle

[ricsearle]

Typical, I struggle with this for a day, and then five minutes after posting here, I figure it out...

So for anyone else experiencing this problem:

You have to set the --host option on the run.sh script. E.g.:

./run.sh -c all --host=192.168.2.2

Hope that helps someone!

Ric

[crl42]

I got the same problem and I don't want to modify the startup script, so I worked more till I found the origin of error.
The problem is in binding the ANY_ADDR 0.0.0.0 to multicast socket on a linux kernel with ipv6 enabled.
If you disable ipv6 from kernel the binding of multicast is ok and the services related to 'all' configuration runs smooth.

[nutulapatisyam]

HI Thanks for posting this, I have another question how does the other server know to replicate the session info.

I have it set it as HTTP Session Replication. When both servers come up they think they are only 1 member in the cluster.

regards
syam nutulapati

[smickerm]

Thanks Ric it helped me!

[miek]

rather than turn off in kernel you may want to use this.
JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true"