Skip to content

Issue 1528: enable native access to silence JNA warning on Java 25+ - #80

Open
labkey-willm wants to merge 1 commit into
developfrom
fb_jna_native_access_1528
Open

Issue 1528: enable native access to silence JNA warning on Java 25+#80
labkey-willm wants to merge 1 commit into
developfrom
fb_jna_native_access_1528

Conversation

@labkey-willm

@labkey-willm labkey-willm commented Aug 25, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Appends --enable-native-access=ALL-UNNAMED to JAVA_REFLECTION_JAR_OPS in 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
  • Manual: run install script fresh on a test EC2 instance, confirm tomcat_lk.service's JAVA_REFLECTION_JAR_OPS includes the new flag and the JNA warning no longer appears in logs when the docker module is active

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant