-
-
Notifications
You must be signed in to change notification settings - Fork 15.8k
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
In netty-4.1.28.Final version, an error occurs when running on jdk6. #8166
Milestone
Comments
koo-taejin
added a commit
to koo-taejin/netty
that referenced
this issue
Aug 2, 2018
description Fixed problem loading class included in java7+ when using java6
normanmaurer
added a commit
that referenced
this issue
Aug 2, 2018
Motivation: 952eeb8 introduced the possibility to use any JDK SocketOption when using the NIO transport but broke the possibility to use netty with java6. Modifications: Do not use java7 types in method signatures of the static methods in NioChannelOption to prevent class-loader issues on java6. Result: Fixes #8166.
@koo-taejin PTAL #8168 |
normanmaurer
added a commit
that referenced
this issue
Aug 2, 2018
Motivation: 952eeb8 introduced the possibility to use any JDK SocketOption when using the NIO transport but broke the possibility to use netty with java6. Modifications: Do not use java7 types in method signatures of the static methods in NioChannelOption to prevent class-loader issues on java6. Result: Fixes #8166.
normanmaurer
added a commit
that referenced
this issue
Aug 3, 2018
Motivation: 952eeb8 introduced the possibility to use any JDK SocketOption when using the NIO transport but broke the possibility to use netty with java6. Modifications: Do not use java7 types in method signatures of the static methods in NioChannelOption to prevent class-loader issues on java6. Result: Fixes #8166.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Actual behavior
Steps to reproduce
Netty version
netty-4.1.28.Final
JVM version (e.g.
java -version
)1.6.0_45
OS version (e.g.
uname -a
)Windows10, CentOS 6.6
I think this issue is problem, but I'm not sure.
If this issue is problem, May I make a correction?
The text was updated successfully, but these errors were encountered: