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

Delayed synchronization SSL context initialization in HttpUrlConnector affects functionality #4815

Open
2368001770 opened this issue Jun 29, 2021 · 5 comments

Comments

@2368001770
Copy link

Is there a bug with jersey2.34?I found that “DEFAULT_SSL_SOCKET_FACTORY.get()” and "HttpsURLConnection.getDefaultSSLSocketFactory()" are not always equal.
image

@jansupol
Copy link
Contributor

There is #4757 that requests the context to be initialized lazily.
There is #4566 that requests the context to be initialized statically.
There is an issue with the native image that requests the context to be initialized lazily.

There seem to be a lot of contra requirements.

@senivam
Copy link
Contributor

senivam commented Aug 12, 2021

error message for static (not lazy) default SSL socket factory initialization when used with GraalVM native image:

com.oracle.svm.core.util.UserError$UserException: No instances of sun.security.provider.NativePRNG are allowed in the image heap as this class should be initialized at image runtime. To see how this object got instantiated use --trace-object-instantiation=sun.security.provider.NativePRNG.

@jansupol
Copy link
Contributor

Related: #3293

@jansupol
Copy link
Contributor

jansupol commented Jun 9, 2023

#4332

@dtbaum
Copy link
Contributor

dtbaum commented Oct 29, 2023

This issue is fixed in 2.41 (see PR: #5359)

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

No branches or pull requests

4 participants