Issue 1528: enable native access to silence JNA warning on Java 25+ - #80
Open
labkey-willm wants to merge 1 commit into
Open
Issue 1528: enable native access to silence JNA warning on Java 25+#80labkey-willm wants to merge 1 commit into
labkey-willm wants to merge 1 commit into
Conversation
Appends --enable-native-access=ALL-UNNAMED to JAVA_REFLECTION_JAR_OPS in the embedded-Tomcat systemd unit. JNA (pulled in transitively by docker-java for the docker module) calls System.load, which JEP 472 now flags as a restricted method — this tells the JVM native access is expected.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--enable-native-access=ALL-UNNAMEDtoJAVA_REFLECTION_JAR_OPSin the embedded-Tomcat systemd unit template, so fresh EC2 appserver installs don't emit the JNA/docker-java restricted-native-access warning under Java 25+ (JEP 472).Companion PRs for the other two launch paths:
Related to https://github.com/LabKey/kanban/issues/1528
Test plan
bash -n install-labkey.bash— syntax OK