[
https://issues.apache.org/jira/browse/SOLR-17001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770095#comment-17770095
]
Shawn Heisey commented on SOLR-17001:
-------------------------------------
Seems that the error I was running into (-Xss256k was unexpected at this time)
is also happening on Windows with completely unmodified source, both in
branch_9x and main. I couldn't figure out why that happens because the echo
commands I tried to insert were not executed, so apparently I do not understand
enough about the overall solr.cmd script.
I believe that the patch is correct, but until the other problem is solved, I
cannot be 100% sure about that.
> Adjust workaround for JDK17 bug so it only applies to specific versions with
> the bug
> ------------------------------------------------------------------------------------
>
> Key: SOLR-17001
> URL: https://issues.apache.org/jira/browse/SOLR-17001
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Affects Versions: 9.3
> Reporter: Shawn Heisey
> Assignee: Shawn Heisey
> Priority: Minor
> Labels: patch
> Attachments: SOLR-17001-1.patch, SOLR-17001.patch
>
>
> SOLR-16463 added a workaround in the bin/solr and bin\solr.cmd scripts for a
> bug in JDK 17 and 19. That workaround assumes that any Java version 17 or
> later is affected.
> At the time the workaround was implemented, there were no released Java
> versions without the bug. Now there are.
> This issue will add detection for good and bad Java versions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
