1 Reply Latest reply on Dec 5, 2006 10:40 PM by Tom Elrod

    Better support for multi-homing

    Scott Stark Master

      Consider this connector config:

      <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="numAcceptThreads">1</attribute>
       <attribute name="maxPoolSize">303</attribute>
       <attribute name="clientMaxPoolSize" isParam="true">304</attribute>
       <attribute name="socketTimeout">60000</attribute>
       <attribute name="serverBindAddress">192.168.0.82</attribute>
       <attribute name="serverBindPort">6666</attribute>
       <attribute name="clientConnectAddress">216.23.33.2</attribute>
       <attribute name="clientConnectPort">7777</attribute>
       <attribute name="enableTcpNoDelay" isParam="true">false</attribute>
       <attribute name="backlog">200</attribute>
       </invoker>
      
       <handlers>
       <handler subsystem="mock">
       org.jboss.remoting.transport.mock.MockServerInvocationHandler
       </handler>
       </handlers>
       </config>
       </attribute>
      
      </mbean>
      


      What I would like to see supported is

      <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="numAcceptThreads">1</attribute>
       <attribute name="maxPoolSize">303</attribute>
       <attribute name="clientMaxPoolSize" isParam="true">304</attribute>
       <interfaces>
       <interface name="eth0">
       <attribute name="socketTimeout">60000</attribute>
       <attribute name="serverBindAddress">192.168.0.82</attribute>
       <attribute name="serverBindPort">6666</attribute>
       <attribute name="clientConnectAddress">216.23.33.2</attribute>
       <attribute name="clientConnectPort">7777</attribute>
       <attribute name="enableTcpNoDelay" isParam="true">false</attribute>
       <attribute name="backlog">200</attribute>
       </interface>
       <interface name="eth1">
       <attribute name="socketTimeout">60000</attribute>
       <attribute name="serverBindAddress">192.168.10.10</attribute>
       <attribute name="serverBindPort">6666</attribute>
       <attribute name="clientConnectAddress">216.23.10.2</attribute>
       <attribute name="clientConnectPort">7777</attribute>
       <attribute name="enableTcpNoDelay" isParam="true">false</attribute>
       <attribute name="backlog">200</attribute>
       </interface>
       </interfaces>
       </invoker>
      
       <handlers>
       <handler subsystem="mock">
       org.jboss.remoting.transport.mock.MockServerInvocationHandler
       </handler>
       </handlers>
       </config>
       </attribute>
      
      </mbean>
      


      so that there is an explicit notion of multi-homing for the handler. A problem with the current legacy and remoting connectors is that setting up multiple interfaces requires multiple connectors.