-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working in 17 JDK #600
Comments
The cause is that creating a new DirectBuffer requires a different implementation for JDK17:
|
Merged
xerial
added a commit
that referenced
this issue
Jun 28, 2022
* Reproduce #600 (JDK17 error) * Add workaround for Java17 * Add a helpful error message * Add note on JDK17
To use DirectByteBuffer in JDK17, two JVM options must be set:
If DirectByteBuffer is not used, msgpack-java 0.9.3 will work even if these two options are not set. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, when i use any unpack* metod ( example messageUnpacker.unpackInt()) i recive error
Unable to make private java.nio.DirectByteBuffer(long,int) accessible: module java.base does not "opens java.nio" to unnamed module @5c30a9b0
Probmlem in org.msgpack.core.buffer.DirectBufferAccess and what does he use java.nio.DirectByteBuffer which is closed
Fast decision by add this when you start the JVM : --add-opens java.base/java.nio=ALL-UNNAMED
but it's a crutch(
I use:
'org.msgpack:msgpack-core:0.9.0'
full stack trace
`
The text was updated successfully, but these errors were encountered: