gpt4 book ai didi

java - 如何修复 'NoClassDefFoundError: Could not initialize class sun.security.ssl.SSLContextImpl$DefaultManagersHolder'

转载 作者:太空宇宙 更新时间:2023-11-03 14:25:24 25 4
gpt4 key购买 nike

我开发的应用程序使用 SSL 连接到外部 API (Zendesk API)。

它过去工作正常,但现在每当应用程序尝试连接到 Zendesk API 时,我们都会收到以下错误:java.net.ConnectException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun .security.ssl.SSLContextImpl$DefaultSSLContext)NoClassDefFoundError: Could not initialize class sun.security.ssl.SSLContextImpl$DefaultManagersHolder 引起。

我们在 Debian 8.11 上使用 Java 1.7.0_231。

我在互联网上找不到任何解决方案。

我已经检查了凭据:它们是正确的。

根据我在 Internet 上发现的信息,此错误可能是由缺少 jar“jsse.jar”引起的,但我已经检查过它存在。

它在另一个环境中运行良好,一个带有 java 1.7.0_211 的 Debian 9.9。

这是堆栈跟踪:

    at com.ning.http.client.providers.netty.future.NettyResponseFuture.abort(NettyResponseFuture.java:231)
at com.ning.http.client.providers.netty.request.NettyConnectListener.onFutureFailure(NettyConnectListener.java:137)
at com.ning.http.client.providers.netty.request.NettyConnectListener.operationComplete(NettyConnectListener.java:145)
at org.jboss.netty.channel.DefaultChannelFuture.notifyListener(DefaultChannelFuture.java:409)
at org.jboss.netty.channel.DefaultChannelFuture.addListener(DefaultChannelFuture.java:145)
at com.ning.http.client.providers.netty.request.NettyRequestSender.sendRequestWithNewChannel(NettyRequestSender.java:284)
at com.ning.http.client.providers.netty.request.NettyRequestSender.sendRequestWithCertainForceConnect(NettyRequestSender.java:142)
at com.ning.http.client.providers.netty.request.NettyRequestSender.sendRequest(NettyRequestSender.java:117)
at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.execute(NettyAsyncHttpProvider.java:87)
at com.ning.http.client.AsyncHttpClient.executeRequest(AsyncHttpClient.java:506)
at org.zendesk.client.v2.Zendesk.submit(Zendesk.java:1771)
at org.zendesk.client.v2.Zendesk.access$1300(Zendesk.java:91)
... 90 more
Caused by: java.net.ConnectException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
at com.ning.http.client.providers.netty.request.NettyConnectListener.onFutureFailure(NettyConnectListener.java:133)
... 100 more
Caused by: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
at java.security.Provider$Service.newInstance(Provider.java:1256)
at sun.security.jca.GetInstance.getInstance(GetInstance.java:236)
at sun.security.jca.GetInstance.getInstance(GetInstance.java:164)
at javax.net.ssl.SSLContext.getInstance(SSLContext.java:156)
at javax.net.ssl.SSLContext.getDefault(SSLContext.java:97)
at com.ning.http.util.SslUtils.getSSLContext(SslUtils.java:70)
at com.ning.http.client.SSLEngineFactory$DefaultSSLEngineFactory.newSSLEngine(SSLEngineFactory.java:49)
at com.ning.http.client.providers.netty.channel.ChannelManager.createSslHandler(ChannelManager.java:401)
at com.ning.http.client.providers.netty.channel.SslInitializer.connectRequested(SslInitializer.java:44)
at org.jboss.netty.channel.SimpleChannelDownstreamHandler.handleDownstream(SimpleChannelDownstreamHandler.java:88)
at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784)
at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:54)
at org.jboss.netty.handler.codec.http.HttpClientCodec.handleDownstream(HttpClientCodec.java:97)
at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784)
at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleDownstream(ChunkedWriteHandler.java:109)
at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582)
at org.jboss.netty.channel.Channels.connect(Channels.java:634)
at org.jboss.netty.channel.AbstractChannel.connect(AbstractChannel.java:216)
at org.jboss.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:229)
at org.jboss.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:182)
at com.ning.http.client.providers.netty.request.NettyRequestSender.connect(NettyRequestSender.java:377)
at com.ning.http.client.providers.netty.request.NettyRequestSender.sendRequestWithNewChannel(NettyRequestSender.java:283)
... 96 more
Caused by: java.lang.NoClassDefFoundError: Could not initialize class sun.security.ssl.SSLContextImpl$DefaultManagersHolder
at sun.security.ssl.SSLContextImpl$DefaultSSLContext.<init>(SSLContextImpl.java:1006)
at sun.reflect.GeneratedConstructorAccessor559.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.security.Provider$Service.newInstance(Provider.java:1237)
... 120 more

感谢任何帮助。

最佳答案

这个错误是在最近更新 openjdk 的 debian 软件包时引入的,版本 7u231-2.6.19-1~deb8u1。它在版本 7u231-2.6.19-1~deb8u2 中得到修复。

参见 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935082 .

关于java - 如何修复 'NoClassDefFoundError: Could not initialize class sun.security.ssl.SSLContextImpl$DefaultManagersHolder',我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/57654768/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com