[jboss-jira] [JBoss JIRA] Commented: (JBREM-749) BisocketServerInvoker: Make configurable the address and port of secondary server socket

Ron Sigal (JIRA) jira-events at lists.jboss.org
Wed Aug 22 19:10:31 EDT 2007


    [ http://jira.jboss.com/jira/browse/JBREM-749?page=comments#action_12373420 ] 
            
Ron Sigal commented on JBREM-749:
---------------------------------

The address to which the secondary ServerSocket is bound is now the same as that to which the "primary" ServerSocket is bound. The address sent to the client to use in connecting to the secondary ServerSocket is taken from the server's InvokerLocator.  It follows that if the "clientConnectAddress" property is set, its value will be used for the secondary ServerSocket.  

Also, there are two new configurable parameters in the class org.jboss.remoting.transport.bisocket.Bisocket specific to the bisocket transport:

Code:

   public static final String SECONDARY_BIND_PORT = "secondaryBindPort";
   public static final String SECONDARY_CONNECT_PORT = "secondaryConnectPort";
	

SECONDARY_BIND_PORT determines which port the secondary ServerSocket binds to, and SECONDARY_CONNECT_PORT determines which port is sent to the client to use in connecting to the secondary ServerSocket. 

There are two advantages to the new configuration properties.  

1. Being able to specify the secondary connect address makes it possible to run a bisocket server behind a NAT router.

2. Being able to specify the secondary bind port makes it possible to run a bisocket server behind a firewall.

The changes have been implemented for the 2.2.2.GA release.  They need to be applied to the remoting_2_x branch.

Unit test:  org.jboss.test.remoting.callback.pull.UniqueCallbackPollerTestCase.

> BisocketServerInvoker: Make configurable the address and port of secondary server socket
> ----------------------------------------------------------------------------------------
>
>                 Key: JBREM-749
>                 URL: http://jira.jboss.com/jira/browse/JBREM-749
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP4, 2.2.1.GA
>            Reporter: Takayoshi Kimura
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA
>
>
> This is a feature request for someone who needs to fix the secondary port used by the bisocket protocol.
> In 2.2.0.GA, it is not configurable:
>          InetAddress host = getServerSocket().getInetAddress();
>          int freePort = PortUtil.findFreePort(host.getHostAddress());

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list