Bisocket configuration update
This page addresses bisocket transport configuration parameters made available after the version of the Remoting Guide associated with the Remoting 2.2.0.GA release. This information is current as of Release 2.2.2.SP2. Please check the Remoting Guide for additional information.
The following parameters have been added. The string values are found in the class org.jboss.remoting.transport.bisocket.Bisocket:
MAX_CONTROL_CONNECTION_RESTARTS (actual value "maxControlConnectionRestarts"): determines the number of times the BisocketServerInvoker.ControlMonitorTimerTask running in a callback server invoker (i.e., on the client side) will restart a control connection after failing to receive a ping from the server within the expected window. The default value is 10.
SECONDARY_BIND_PORT (actual value "secondaryBindPort"): determines the port to which the secondary server socket will be bound. The default behavior is to find an available anonymous port.
SECONDARY_CONNECT_PORT (actual value "secondaryConnectPort"): determines the secondary server socket port which will be communicated to the client side. The default behavior is to use the secondary server socket bind port.
1. There are two advantages to the introduction of the "secondaryBindPort" and "secondaryConnectPort" parameters:
a. Being able to specify the secondary bind port makes it possible to run a bisocket server behind a firewall
b. Being able to specify the secondary connect address makes it possible to run a bisocket server behind a NAT router
2. The host to which the secondary server socket is bound is determined by the "serverBindAddress" property (available to all transports), and the host communicated to the client for connecting to the secondary server socket is determined by the "clientConnectAddress" property (also available to all transport).