Skip to content
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

disable socket factory pre JDK8u242 #5915

Conversation

PennyAndWang
Copy link
Contributor

@PennyAndWang PennyAndWang commented Nov 11, 2020

Hi, my presto version is 0.214 and my upgrade plan is in progress . At 0.214 , I hit the same issue: #1169 and it was fixed by this PR :#2633 . But this PR is ok for JDK11 or later, It will slow down of presto-cli and presto-jdbc in some JDK8 environment, for example JDK8u261.
The codes still need to be optimized. According to this link: https://www.eclipse.org/jetty/documentation/current/alpn-chapter.html , I think It shoud be like this :return StandardSystemProperty.JAVA_VERSION.value().compareTo("1.8.0_242") > 0; so I commit this PR.
I tested the code ,it works fine in JDK8u261.
I know the prestosql current version no longer supports jdk8, so I don't know wether this PR is necessary or not .
Please review , thx!

@electrum
Copy link
Member

Thanks for the PR. At this point, I think we should remove SocketChannelSocketFactory entirely, since it was added to fix an obscure IPv6 bug on macOS, but it now causes problems on newer JDKs. Can you change this PR to remove it?

You can change the commit title to something like

Remove unnecessary SocketChannelSocketFactory

@PennyAndWang
Copy link
Contributor Author

Thanks for the PR. At this point, I think we should remove SocketChannelSocketFactory entirely, since it was added to fix an obscure IPv6 bug on macOS, but it now causes problems on newer JDKs. Can you change this PR to remove it?

You can change the commit title to something like

Remove unnecessary SocketChannelSocketFactory
@electrum ok, thank you for your reply. I will submit a new PR soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

2 participants