Delayed synchronization SSL context initialization in HttpUrlConnector affects functionality
Is there a bug with jersey2.34?I found that “DEFAULT_SSL_SOCKET_FACTORY.get()” and "HttpsURLConnection.getDefaultSSLSocketFactory()" are not always equal.

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.
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.
Related: #3293
#4332
This issue is fixed in 2.41 (see PR: #5359)