Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Replace Unsafe and illegal reflection operations

See original GitHub issue

Gave a quick try to lmdbjava with JDK 9 and wanted to record the findings here.

Due the the class access restrictions imposed by Jigsaw, the following JVM arguments have to be specified:

--add-opens java.base/java.nio=ALL-UNNAMED --add-opens java.base/sun.nio.ch=ALL-UNNAMED

Issue Analytics

State:
Created 7 years ago
Reactions:5
Comments:31 (17 by maintainers)

Top GitHub Comments

7reactions

benalexaucommented, Aug 17, 2021

Commit 5687bd61ff8de770800fa319b4b98a0f61a92b24 shows how to add the required JVM parameters for running tests in Maven builds etc. It’s implemented as a profile as we presently perform CI builds with Java 8.

https://openjdk.java.net/jeps/412 looks a promising pathway for Java 17 and above, particularly given Java 17 is LTS.

How would people feel about LmdbJava 1.x targeting Java 16 and below, with LmdbJava 2.x requiring Java 17 and above? This would draw a line in the sand and allow use of newer APIs.

7reactions

jubaxcommented, Jun 27, 2019

I just wanted to ask if there is any progress on this issue. I’m using

--add-opens java.base/java.nio=ALL-UNNAMED --add-opens java.base/sun.nio.ch=ALL-UNNAMED where possible, but in some cases I cannot do that and then the “illegal reflective access” warnings show up. BTW: Does anybody know how to get rid of the warnings without the commandline arguments?