[
https://issues.apache.org/jira/browse/SOLR-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17987296#comment-17987296
]
Jan Høydahl edited comment on SOLR-17641 at 7/1/25 11:03 PM:
-------------------------------------------------------------
Today, if you try to run Solr main on JRE24, startup fails to start, with this
output:
{code:bash}
$ bin/solr start
Waiting up to 180 seconds to see Solr running on port 8983 [|]
{code}
Solr never starts, the 180 s times out and if you look into solr.log you'll see
this:
{code:bash}
OpenJDK 64-Bit Server VM warning: -XX:+UseLargePages not supported in this VM
WARNING: Using incubator modules: jdk.incubator.vector
Error occurred during initialization of VM
java.lang.Error: A command line option has attempted to allow or enable the
Security Manager. Enabling a Security Manager is not supported.
at java.lang.System.initPhase3([email protected]/System.java:1947)
{code}
However, if you start Solr with JSM explicitly disabled, it starts as normal
{code:bash}
SOLR_SECURITY_MANAGER_ENABLED=false bin/solr start
...
2025-07-01 22:22:41.227 INFO (main) [c: s: r: x: t:]
o.a.s.s.CoreContainerProvider ___ _ Welcome to Apache Solr™ version
10.0.0-SNAPSHOT 535c6614a1a43907af823a5afbf964e7826c8b25 [snapshot build,
details omitted]
{code}
So the minimal change we can do to "Support Java 24" is to merge PR #3153,
letting our start script disable JSM when detecting Java 24+. It solves this
JIRA's intention. And give users who want/need JSM support for it with Java 21
even in Solr 10.
It will also give the commnity some time to decide on options for SIP-24. We
can then remove the entire JSM support at our time of choosing.
was (Author: janhoy):
Today, if you try to run Solr main on JRE24, startup fails to start, with this
output:
{code:bash}
$ bin/solr start
Waiting up to 180 seconds to see Solr running on port 8983 [|]
{code}
Solr never starts, the 180 s times out and if you look into solr.log you'll
see this:
{code:bash}
OpenJDK 64-Bit Server VM warning: -XX:+UseLargePages not supported in this VM
WARNING: Using incubator modules: jdk.incubator.vector
Error occurred during initialization of VM
java.lang.Error: A command line option has attempted to allow or enable the
Security Manager. Enabling a Security Manager is not supported.
at java.lang.System.initPhase3([email protected]/System.java:1947)
{code}
However, if you start Solr with JSM explicitly disabled, it starts as normal
{code:bash}
SOLR_SECURITY_MANAGER_ENABLED=false bin/solr start
...
2025-07-01 22:22:41.227 INFO (main) [c: s: r: x: t:]
o.a.s.s.CoreContainerProvider ___ _ Welcome to Apache Solr™ version
10.0.0-SNAPSHOT 535c6614a1a43907af823a5afbf964e7826c8b25 [snapshot build,
details omitted]
{code}
So the minimal change we can do to "Support Java 24" is to have our start
script disable JSM when detecting Java 24+. This is a three-line change in
bin/solr, and will solve this JIRA's intention. And give users who want/need
JSM support for it with Java 21 even in Solr 10.
It will also give the commnity some time to decide on options for SIP-24. We
can then remove the entire JSM support at our time of choosing.
> Support Java 24
> ---------------
>
> Key: SOLR-17641
> URL: https://issues.apache.org/jira/browse/SOLR-17641
> Project: Solr
> Issue Type: Bug
> Components: SolrCLI, Tests
> Reporter: Houston Putman
> Assignee: Eric Pugh
> Priority: Critical
> Labels: pull-request-available
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> The main thing here is to disable the Security Manager for Java 24+, both for
> the CLI and testing.
> Reference: https://github.com/apache/lucene/issues/14184
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
