Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Strong encapsulation warning in Java 25.

Open
#9,937 2 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java

Research direction

Start with the dd-agent launch path and the com.kenai.jffi.internal.StubLoader warning described in the report. Determine whether the JFFI dependency can avoid the Java 25 warning without --enable-native-access; the work is done when Java 25 runs without the warning and tracer functionality remains intact.

Written by the indexing model from the issue text.

Description

type: bug report
Tracer Version(s)

1.54.0

Java Version(s)

25.0.1+8.0.LTS

JVM Vendor

Eclipse Adoptium / Temurin

Bug Report

When running dd-agent with Java 25 we get the following warning:

WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::load has been called by com.kenai.jffi.internal.StubLoader in an unnamed module (file:/usr/local/datadog-agent.jar)
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled

From my understanding this won't affect the functionality of the tracer agent right now. But in future versions of Java this might be blocked instead of a warning.

Addiotionally for us using --enable-native-access isn't an option as it might weaken security.

I don't know if migrating from JFFI to Javas Panama would be a viable option?

Expected Behavior

Running dd-agent in Java 25 without the warning.

Reproduction Code

No response

Dominant language
Java
Stars
737
Forks
361
Avg merge
3d 20h
Merged PRs (30d)
173

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DataDog/dd-trace-java

All issues in DataDog/dd-trace-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.