You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mikhail Khludnev (JIRA)" <ji...@apache.org> on 2017/04/01 19:56:41 UTC

[jira] [Updated] (SOLR-9745) SolrCLI swallows errors from solr.cmd

     [ https://issues.apache.org/jira/browse/SOLR-9745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikhail Khludnev updated SOLR-9745:
-----------------------------------
    Summary: SolrCLI swallows errors from solr.cmd  (was: bin/solr* swallows errors from running example instances at least)

> SolrCLI swallows errors from solr.cmd
> -------------------------------------
>
>                 Key: SOLR-9745
>                 URL: https://issues.apache.org/jira/browse/SOLR-9745
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Server
>    Affects Versions: 6.3, master (7.0)
>            Reporter: Mikhail Khludnev
>            Assignee: Mikhail Khludnev
>              Labels: newbie, newdev
>         Attachments: SOLR-9745.patch, SOLR-9745.patch
>
>
> It occurs on mad scenario in LUCENE-7534:
> * solr.cmd weren't granted +x (it happens under cygwin, yes)
> * coolhacker worked it around with cmd /C solr.cmd start -e ..
> * but when SolrCLI runs solr instances with the same solr.cmd, it just silently fails
> I think we can just pass ExecuteResultHandler which will dump exception to console. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org