lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Commented] (SOLR-9046) solr.cmd wrongly assumes Jetty will always listen on
Date Wed, 27 Apr 2016 20:21:13 GMT


Uwe Schindler commented on SOLR-9046:

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, 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
> ------------------------------------------------------------
>                 Key: SOLR-9046
>                 URL:
>             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 (all interfaces). When you change the interface
> address, say to, then the status and stop commands will fail.
> This patch adds a property in, which is passed to SOLR_OPTS as,
and replaces the instances of 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message