[
https://issues.apache.org/jira/browse/SOLR-17746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17986145#comment-17986145
]
Rahul Goswami edited comment on SOLR-17746 at 6/25/25 1:57 PM:
---------------------------------------------------------------
[~hossman] FWIW passing multiple space separated args in --jvm-opts as shown
below *does* work on Windows post the fix in
https://issues.apache.org/jira/browse/SOLR-7962
--jvm-opts "
-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:18983
-Dsolr.myprops.custom=hello"
I remember it not working on Linux since the parsing in SolrCLI is different,
but might need to check again.
was (Author: [email protected]):
[~hossman] FWIW passing multiple space separated args in --jvm-opts as shown
below **does** work on Windows post the fix in
https://issues.apache.org/jira/browse/SOLR-7962
--jvm-opts "
-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:18983
-Dsolr.myprops.custom=hello"
I remember it not working on Linux since the parsing in SolrCLI is different,
but might need to check again.
> bin/solr always fails if you attempt to use --jettyconfig (aka "-j")
> --------------------------------------------------------------------
>
> Key: SOLR-17746
> URL: https://issues.apache.org/jira/browse/SOLR-17746
> Project: Solr
> Issue Type: Bug
> Reporter: Chris M. Hostetter
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The "-jettyconfig" optiona (aka "-j") is documented as...
> {noformat}
> -j <jettyParams> Additional parameters to pass to Jetty when starting
> Solr.
> For example, to add configuration folder that jetty
> should read
> you could pass: -j
> "--include-jetty-dir=/etc/jetty/custom/server/"
> In most cases, you should wrap the additional
> parameters in double quotes.
> {noformat}
> ..but if you actually attempt to run use that example option, you will get
> an error...
> {noformat}
> ./bin/solr start ... -j "--include-jetty-dir=/etc/jetty/custom/server/"
> ERROR: Jetty config is required when using the -j option!
> {noformat}
> IIUC this is because the bash code for parsing this option requires that it
> not start with a "{{\-}}" character; but by definition any option you want to
> pass to jetty will start with "{{\--}}".
> Attempting to workaround this problem by using two sets of quotes doesn't
> seem to work -- the inner quotes are passed verbatim to jetty which seems to
> prevent jetty from recognizing it as a valid option.
> A workaround that *does* seem to work (in my limited testing) is to include a
> leading space character _inside_ the quotes...
> {noformat}
> ./bin/solr start ... -j " --include-jetty-dir=/etc/jetty/custom/server/"
> {noformat}
> ...because for some reason that does *NOT* seem to be passed verbatim.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
