HA JNDI and Multi-homed machine

[chubinator]

In clustering-service.xml, I have specified both the RmiPort and Port for the HANamingService.

I have specified the RmiPort as 21111 and the Port as 21100.

I also specified the BindAddress to the appropriate interface.

The server starts up, but a netstat shows that it bound 21100 to the interface specified and 21111 to *.

The problem is, we are bringing this server up in a cluster and when the other servers attempt to connect to 21111 they fail as they attempt to connect to the externally facing interface, something not possible in our environment.

Likewise, I can't seem to specify a bind address for 24444, our RMIObjectPort.

Any help would be greatly appreciated.

Thanks,
Mark

[chubinator]

Thinking I should probably simplify this question:

How can I tell JBoss to bind the HANamingService RMIPort and RMIObjectPort to a specific interface?

When I specify the BindAddress, it only results in the HA JNDI port being bound to the specified interface and not the other two ports.

Thanks,
Mark

[slaboure]

This has been recently fixed in Branch_3_2

Cheers,


sacha

[chubinator]

Thanks! In fact, I work for the client that submitted the change request via Jboss support, so I was informed of the change.

It appears to have worked as the NamingService binds correctly, but now we are getting a different error soon after the cluster view updates.

Attached is a snippet from the log file.

We are now using the latest snapshot of 3.2.2RC3

Any help is greatly appreciated.

Thanks,
Mark