We have a JBoss 3.2.0 server running on a Windows 2000 multi-homed host. It has a management address 172.* and an application address 10.*.
Currently, the naming service keeps binding to the management address, making it impossible for the application clients to connect.
I tried specifying a BindAddress attribute in the naming service MBean using the 10.* address for the attribute value, but it seems to override it with the Management address.
Without the command line --host=<host or ip> option, I am not sure how to get the service bound to right socket.
Think we got it.