[
https://issues.apache.org/jira/browse/SOLR-17005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770800#comment-17770800
]
Shawn Heisey commented on SOLR-17005:
-------------------------------------
I at least found the problem code.
{code:java}
IF NOT "%SCRIPT_SOLR_OPTS%"=="" (
@echo SOLR_OPTS (SCRIPT) = %SCRIPT_SOLR_OPTS%
){code}
The first line is where the problem happens. If I add the line {{{}echo
'%SCRIPT_SOLR_OPTS%{}}}' right before the IF it outputs {{'-Xss256k
-Dsolr.jetty.host=127.0.0.1'}} .. no leading or trailing spaces to screw things
up. And the test has surrounding quotes, so this really shouldn't be a problem.
> Running 'bin\solr.cmd start' fails with "-Xss256k was unexpected at this time"
> ------------------------------------------------------------------------------
>
> Key: SOLR-17005
> URL: https://issues.apache.org/jira/browse/SOLR-17005
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Affects Versions: main (10.0), 9.4
> Reporter: Shawn Heisey
> Priority: Blocker
> Labels: scripts
> Fix For: 9.4
>
>
> On both branch_9x and main, unmodified, Solr will not start on Windows. It
> produces the error "-Xss256k was unexpected at this time".
> Problem was definitely caused by the commit for SOLR-16970 .
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
