[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1139) Modify PortUtil to allow a configurable range for MIN_UNPRIVILEGED_PORT and MAX_LEGAL_PORT.

[Ron Sigal (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBREM-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12477964#action_12477964 ] 

Ron Sigal commented on JBREM-1139:
----------------------------------

The range from which PortUtil will choose ports may now be modified per JVM.

The parameters

 org.jboss.remoting.transport.PortUtil.MIN_PORT (actual value "minPort")
 org.jboss.remoting.transport.PortUtil.MAX_PORT (actual value "maxPort")

can be added to

 (1) the InvokerLocator,
 (2) a configuration map passed to org.jboss.remoting.Client or org.jboss.remoting.transport.Connector, or
 (3) the Connector's MBean definition

and they will be used to set the range used by PortUtil (determined by PortUtil.minPort and PortUtil.maxPort).  Note that PortUtil.minPort and PortUtil.maxPort are static values, so setting them affects all other clients and servers in the JVM.  Also, the values will be updated only if the resulting range is more restrictive.  I.e.,

 PortUtil.minPort == 3000  and  PortUtil.maxPort == 50000

can be updated to

 PortUtil.minPort == 4000  and  PortUtil.maxPort == 40000

but not to

 PortUtil.minPort == 2000 and  PortUtil.maxPort == 60000.

So far, the changes have been added to branch 2.2.  As usual in Remoting 2.2.x, the values in InvokerLocator take precedence over the values in the configuration map.

Unit tests:

  * org.jboss.test.remoting.util.PortUtilRangeOnClientTestCase
  * org.jboss.test.remoting.util.PortUtilRangeOnServerTestCase
  * org.jboss.test.remoting.util.PortUtilRangeOnServerWithXMLTestCase

Still have to apply changes to branch 2.x.

> Modify PortUtil to allow a configurable range for MIN_UNPRIVILEGED_PORT and MAX_LEGAL_PORT.
> -------------------------------------------------------------------------------------------
>
>                 Key: JBREM-1139
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1139
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.5.1 (Flounder), 2.2.3
>            Reporter: Colin Mondesir
>            Assignee: Ron Sigal
>             Fix For: 2.5.2 (Flounder), 2.2.3.SP1
>
>
> PortUtil could be improved to read the port range configuration.
> This is straightforward and no side effect is expected.  However,
> PortUtil and its callers will need some refactoring as it is just a
> static utility classes currently.

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