[
https://issues.apache.org/jira/browse/SOLR-9046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260862#comment-15260862
]
Uwe Schindler commented on SOLR-9046:
-------------------------------------
Hi,
I patched my checkout (master) locally. I am already testing (including all
"bad" things like whitespace in path name). There are two thing that might not
work - I am checking this, too:
- It assumes that JETTY_HOST is an ip address. You can always also give a
hostname. It should be documented in the new solr.cmd.in, that you have to use
an IP address
- It might not work with IPv6. As I am working in an IPv6 environment - IPv4
works, but is not preferred here anymore, I will report on bugs, too.
> 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: Timothy Potter
> 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: [email protected]
For additional commands, e-mail: [email protected]
