You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Bram Van Dam (JIRA)" <ji...@apache.org> on 2016/04/27 21:07:12 UTC
[jira] [Updated] (SOLR-9046) solr.cmd wrongly assumes Jetty will
always listen on 0.0.0.0
[ https://issues.apache.org/jira/browse/SOLR-9046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bram Van Dam updated SOLR-9046:
-------------------------------
Attachment: SOLR-9045.patch
> solr.cmd wrongly assumes Jetty will always listen on 0.0.0.0
> ------------------------------------------------------------
>
> Key: SOLR-9046
> URL: https://issues.apache.org/jira/browse/SOLR-9046
> Project: Solr
> Issue Type: Bug
> Components: Server
> Affects Versions: 5.5
> Environment: Windows
> Reporter: Bram Van Dam
> Fix For: 5.5.1
>
> Attachments: SOLR-9045.patch
>
>
> The Windows solr.cmd script makes the (incorrect) assumption that Solr will always be listening on 0.0.0.0 (all interfaces). When you change the interface
> address, say to 127.0.0.1, then the status and stop commands will fail.
> This patch adds a property in solr.in.cmd, which is passed to SOLR_OPTS as -Djetty.host, and replaces the instances of 0.0.0.0 in solr.cmd.
> The patch includes some changes in the netstat logic used in solr.cmd to find the correct Solr process(es).
> Tested on Solr 5.5 on Windows 7 and 10.
> Note: Untested on Solr 6. Currently using Solr 5.5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org