[
https://issues.apache.org/jira/browse/SOLR-17001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-17001:
--------------------------------
Attachment: SOLR-17001-2.patch
Status: Open (was: Open)
New patch adjusting solr.cmd changes.
* Removes all mention and handling of Java 8, as 11 is the minimum version
required.
* Enables the JIT workaround for Java 11 before 11.0.19. The JDK bug says the
fix was applied to that version.
* Cleaned up handling for OpenJ9 GC logging.
Still says "-Xss256k was unexpected at this time" when trying to run, but this
also happens on unmodified branch_9x and main, it's not because of my changes
here.
Beginning the 'check' run, but as this doesn't touch Java code, I doubt any
failures I see are because of this change.
> 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-2.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]
