[JBoss JIRA] Created: (JBREM-1139) Modify PortUtil to allow a configurable range for MIN_UNPRIVILEGED_PORT and MAX_LEGAL_PORT.
1:46 a.m.
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.2.2.SP8
Reporter: Colin Mondesir
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
3:17 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-1139) Modify PortUtil to allow a configurable range for MIN_UNPRIVILEGED_PORT and MAX_LEGAL_PORT.
[
https://jira.jboss.org/jira/browse/JBREM-1139?page=com.atlassian.jira.plu...
]
Ron Sigal updated JBREM-1139:
-----------------------------
Fix Version/s: 2.5.2 (Flounder)
2.2.3.SP1
Affects Version/s: 2.2.3
2.5.1 (Flounder)
(was: 2.2.2.SP8)
Assignee: Ron Sigal
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
3:56 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-1139) Modify PortUtil to allow a configurable range for MIN_UNPRIVILEGED_PORT and MAX_LEGAL_PORT.
[
https://jira.jboss.org/jira/browse/JBREM-1139?page=com.atlassian.jira.plu...
]
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
10:24 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-1139) Modify PortUtil to allow a configurable range for MIN_UNPRIVILEGED_PORT and MAX_LEGAL_PORT.
[
https://jira.jboss.org/jira/browse/JBREM-1139?page=com.atlassian.jira.plu...
]
Ron Sigal commented on JBREM-1139:
----------------------------------
Committed changes to branch 2.x.
Unit tests:
* org.jboss.test.remoting.util.PortUtilRangeOnClientTestCase
* org.jboss.test.remoting.util.PortUtilRangeOnServerTestCase
* org.jboss.test.remoting.util.PortUtilRangeOnServerWithXMLTestCase
* org.jboss.test.remoting.util.PortUtilRangeOnServerWithServerConfigurationTestCase
Waiting for results in hudson.
Need to update Remoting Guides.
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
7:28 p.m.
New subject: [JBoss JIRA] Closed: (JBREM-1139) Modify PortUtil to allow a configurable range for MIN_UNPRIVILEGED_PORT and MAX_LEGAL_PORT.
[
https://jira.jboss.org/jira/browse/JBREM-1139?page=com.atlassian.jira.plu...
]
Ron Sigal closed JBREM-1139.
----------------------------
Resolution: Done
Tests pass in hudson.
Added paragraph to Section "How the server bind address and port is determined"
in Remoting Guide on branches 2.2. and 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
6191
days inactive
6237
days old
4 comments
2 participants
participants (2)
-
Colin Mondesir (JIRA) -
Ron Sigal (JIRA)