I'm trying other things - specifically using "serverBindAddress" and that seems to work better.
Did something happen to the Jboss/Remoting client such that it no longer uses or refers to "clientConnectAddress"?? No matter what I do, I can't get the client to behave any differently, specifying clientConnectAddress or not - as if it isn't supported on the client anymore.
The fact is that "clientConnectAddress" is used only on the server side by org.jboss.remoting.transport.transport.Connector to generate an InvokerLocator from a declarative XML configuration (e.g., an MBean). So, for example,
<mbean code="org.jboss.remoting.transport.Connector" name="jboss.remoting:service=Connector,transport=Socket" display-name="Socket transport Connector"> <attribute name="Configuration"> <config> <invoker transport="socket"> <attribute name="serverBindAddress">192.168.0.82</attribute> <attribute name="clientConnectAddress">18.104.22.168</attribute> ...
will cause the server to bind to 192.168.0.82 but will lead to the InvokerLocator
It is thus that the value of "clientConnectAddress" is communicated to the client, which looks only at the address in the InvokerLocator.
The discussion in Remoting Guide must be lacking, so I've created JIRA-1142 "Clarify use of "clientConnectAddress" in RemotingGuide" to remind me to extend it.