[ 
https://issues.apache.org/jira/browse/SOLR-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chaiyasit (Sit) Manovit updated SOLR-6791:
------------------------------------------
    Description: 
Due to following two lines of code, it would try to use port number less than 
1024 which are privileged ports

bq. {{-Dcom.sun.management.jmxremote.port=10${SOLR_PORT: -2} \
-Dcom.sun.management.jmxremote.rmi.port=10${SOLR_PORT: -2}"}}

Maybe the prefix should be changed to 20. (Too high a number may risk colliding 
with default port for embedded ZooKeeper.)


  was:
Due to following two lines of code, it would try to use port number less than 
1024 which are privileged ports

-Dcom.sun.management.jmxremote.port=10${SOLR_PORT: -2} \
-Dcom.sun.management.jmxremote.rmi.port=10${SOLR_PORT: -2}"

Maybe the prefix should be changed to 20. (Too high a number may risk colliding 
with default port for embedded ZooKeeper.)



> Solr start script failed when last 2 digits of solr port is less than 24 and 
> run by non-root user
> -------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-6791
>                 URL: https://issues.apache.org/jira/browse/SOLR-6791
>             Project: Solr
>          Issue Type: Bug
>          Components: scripts and tools
>    Affects Versions: 4.10.2
>            Reporter: Chaiyasit (Sit) Manovit
>            Priority: Minor
>
> Due to following two lines of code, it would try to use port number less than 
> 1024 which are privileged ports
> bq. {{-Dcom.sun.management.jmxremote.port=10${SOLR_PORT: -2} \
> -Dcom.sun.management.jmxremote.rmi.port=10${SOLR_PORT: -2}"}}
> Maybe the prefix should be changed to 20. (Too high a number may risk 
> colliding with default port for embedded ZooKeeper.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to