[
https://issues.apache.org/jira/browse/SOLR-9046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261703#comment-15261703
]
Bram Van Dam commented on SOLR-9046:
------------------------------------
Thanks for these fixes and the commit. Just tested your changes on our setup
and everything seems to work.
Windows's netstat doesn't have an option to only display listening processes,
which is why I added the 'find ":0 "'. Without that extra constraint, the stop
process would try to shoot down internet explorer when I was using the admin UI
:-) Whoops!
> 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
> Assignee: Uwe Schindler
> Fix For: master, 5.5.1, 6.1
>
> Attachments: SOLR-9045.patch, SOLR-9046.patch, SOLR-9046.patch,
> SOLR-9046.patch, SOLR-9046.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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
