[
https://issues.apache.org/jira/browse/SOLR-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe resolved SOLR-6928.
------------------------------
Resolution: Fixed
Committed on lucene_solr_4_10.
{quote}
There is a problem with this approach, though, very likely on all branches: the
modified test against netstat output also matches non-listening entries, so
e.g. when using the admin UI, non-listening connections from my web browser
linger after the Solr jetty has died, and the stop code goes into a loop where
it thinks there is still an open Solr process, but can't find the corresponding
.port file. Eventually, the loop terminates (after ~6 iterations in my tests).
I'll make a new issue.
{quote}
I see [~thelabdude] fixed this as part of SOLR-7016, which I'm going to
backport next. I couldn't get this to reproduce on trunk, because processes
not listed by {{netstat}} as on IP {{0.0.0.0}} (where Solr's jetty binds) are
ignored after SOLR-7016.
> solr.cmd stop works only in english
> -----------------------------------
>
> Key: SOLR-6928
> URL: https://issues.apache.org/jira/browse/SOLR-6928
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
> Affects Versions: 4.10.3
> Environment: german windows 7
> Reporter: john.work
> Assignee: Steve Rowe
> Priority: Minor
> Fix For: 4.10.4, Trunk, 5.0
>
> Attachments: SOLR-6928-lucene_solr_4_10.patch, SOLR-6928.patch,
> SOLR-6928.patch
>
>
> in solr.cmd the stop doesnt work while executing 'netstat -nao ^| find /i
> "listening" ^| find ":%SOLR_PORT%"' so "listening" is not found.
> e.g. in german cmd.exe the netstat -nao prints the following output:
> {noformat}
> Proto Lokale Adresse Remoteadresse Status PID
> TCP 0.0.0.0:80 0.0.0.0:0 ABHÖREN 4
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
