-
-
Notifications
You must be signed in to change notification settings - Fork 16k
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
java.lang.ClassNotFoundException: jdk.internal.misc.Unsafe #6855
Milestone
Comments
@ashkanpaya88 ah this was fixed recently and is harmless: Upgrade to 4.1.12.Final and you will not see it anymore |
Great, thank you! |
jimrthy
added a commit
to jimrthy/frereth-cp
that referenced
this issue
Feb 1, 2018
At least it got rid of the annoying startup error that involved a ClassNotFoundException and jdk.internal.misc.Unsafe. c.f. netty/netty#6855. This looked like it was at least in the general vicinity of the core dump that's coming from trying to build-actual-hello-packet. As predicted in that ticket, this really didn't help my actual problem. But it's been something for which I've been itching to find an excuse for quite a while now. No idea whether anything else got broken in the process.
quaxt
added a commit
to quaxt/fulstk
that referenced
this issue
Apr 11, 2020
yada was pulling in an old version of aleph which in turn was pulling in an old version of Netty (4.1.11), which had this issue netty/netty#6855 java.lang.ClassNotFoundException: jdk.internal.misc.Unsafe That exception would appear when running the production Uberjar Updating aleph to 0.4.6, we get netty 4.1.25 (issue was fixed in 4.1.12)
quaxt
added a commit
to quaxt/fulstk
that referenced
this issue
Apr 11, 2020
yada was pulling in an old version of aleph which in turn was pulling in an old version of Netty (4.1.11), which had this issue netty/netty#6855 java.lang.ClassNotFoundException: jdk.internal.misc.Unsafe That exception would appear when running the production Uberjar Updating aleph to 0.4.6, we get netty 4.1.25 (issue was fixed in 4.1.12)
myunghoonju
added a commit
to myunghoonju/myboot
that referenced
this issue
May 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior: No stack trace regarding this class
Actual behavior:
Steps to reproduce
We were using netty 4.0.x branch for long time and once we switch to 4.1.x, this stack trace appeared.
Netty version: 4.1.11.Final
Netty tcnative version: 2.0.1.Final
JVM version (e.g.
java -version
)openjdk version "1.8.0_121"
OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-0ubuntu1.16.04.2-b13)
OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode)
OS version (e.g.
uname -a
)Ubuntu 16.04 and Mac 10.11.4
The text was updated successfully, but these errors were encountered: