questdb / questdb/java-questdb-client
[MINOR] Java 25 - A restricted method in java.lang.System has been called
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 10
- Forks
- 6
- Avg merge
- 6h 40m
- Merged PRs (30d)
- 2
Description
To reproduce
Starting with Java 25 I receive the following message once. There are no problems on using the code, however,
WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::load has been called by io.questdb.client.std.Os in an unnamed module (file:/home/jboss/lib/main/org.questdb.questdb-client-1.2.0.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
There are reports on this for other libraries too, like here https://github.com/jline/jline3/issues/1067#issuecomment-2571591690
questdb-client is 1.2.0
QuestDB version:
7.3.5
OS, in case of Docker specify Docker and the Host OS:
debian trixie
File System, in case of Docker specify Host File System:
ext4
Full Name:
Marco Descher
Affiliation:
n/a
Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?
- Yes, I have
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Java 25 warning to io.questdb.client.std.Os and its call to java.lang.System::load in questdb-client 1.2.0. Reproduce the warning with QuestDB 7.3.5 on Debian trixie, then inspect the client’s native-loading path. Done means the client no longer emits the restricted-method warning under Java 25 without breaking native loading.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100