当前位置: 首页 > 知识库问答 >
问题:

当从wildfly_9.0.2获取请求时,获取了SSLHandshakeException。最终(客户端)到WAS 8.5.5.7(服务器)

袁志专
2023-03-14

当从wildfly_9.0.2获取请求时,获取了SSLHandshakeException。最终(客户端)到WAS 8.5.5.7(服务器)

客户端野蝇满9.0.2。最终的

java版本“1.7.0_131”java(TM)SE运行时环境(构建1.7.0_131-b12)java热点(TM)64位服务器虚拟机(构建24.131-b12,混合模式)

服务器IBM webSphere 8.5.5.7(SSL配置中的SSL_TLS)

Java版本1.7.0Java(TM)SE运行时环境(构建pxa6470_27sr2fp10-20141218_02(SR2 FP10))IBMJ9 VM(构建2.7,JRE 1.7.0Linuxamd64-64压缩引用20141215_227395(启用JIT,AOT启用)J9VM-R27_Java727_SR2_20141215_1631_B227395JIT-tr.r13.java_20141003_74587.07 GC-R27_Java727_SR2_20141215_1631_B227395_CMPRSSJ9CL-20141215_227395)JCL-20141217_01基于Oracle jdk7u75-b12

-贾瓦克斯。网debug=ssl:使用握手

客户端输出:

2017-10-17 14:55:38,874 INFO  [stdout] ([application]-server-thread-3) [application]-server-thread-3, setSoTimeout(0) called
2017-10-17 14:55:38,874 INFO  [stdout] ([application]-server-thread-3) Allow unsafe renegotiation: false
2017-10-17 14:55:38,874 INFO  [stdout] ([application]-server-thread-3) Allow legacy hello messages: true
2017-10-17 14:55:38,874 INFO  [stdout] ([application]-server-thread-3) Is initial handshake: true
2017-10-17 14:55:38,874 INFO  [stdout] ([application]-server-thread-3) Is secure renegotiation: false
2017-10-17 14:55:38,876 INFO  [stdout] ([application]-server-thread-3) %% No cached client session
2017-10-17 14:55:38,876 INFO  [stdout] ([application]-server-thread-3) *** ClientHello, TLSv1.2
2017-10-17 14:55:38,878 INFO  [stdout] ([application]-server-thread-3) RandomCookie:  GMT: 1491398330 bytes = { 127, 152, 179, 107, 241, 111, 83, 100, 130, 161, 79, 60, 11, 160, 102, 93, 97, 100, 20, 238, 3, 103, 143, 176, 164, 81, 92, 146 }
2017-10-17 14:55:38,878 INFO  [stdout] ([application]-server-thread-3) Session ID:  {}
2017-10-17 14:55:38,878 INFO  [stdout] ([application]-server-thread-3) Cipher Suites: [TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
2017-10-17 14:55:38,878 INFO  [stdout] ([application]-server-thread-3) Compression Methods:  { 0 }
2017-10-17 14:55:38,878 INFO  [stdout] ([application]-server-thread-3) Extension elliptic_curves, curve names: {secp256r1, secp384r1, secp521r1, sect283k1, sect283r1, sect409k1, sect409r1, sect571k1, sect571r1, secp256k1}
2017-10-17 14:55:38,879 INFO  [stdout] ([application]-server-thread-3) Extension ec_point_formats, formats: [uncompressed]
2017-10-17 14:55:38,879 INFO  [stdout] ([application]-server-thread-3) Extension signature_algorithms, signature_algorithms: SHA512withECDSA, SHA512withRSA, SHA384withECDSA, SHA384withRSA, SHA256withECDSA, SHA256withRSA, SHA256withDSA, SHA224withECDSA, SHA224withRSA, SHA224withDSA, SHA1withECDSA, SHA1withRSA, SHA1withDSA
2017-10-17 14:55:38,879 INFO  [stdout] ([application]-server-thread-3) ***
2017-10-17 14:55:38,879 INFO  [stdout] ([application]-server-thread-3) [application]-server-thread-3, WRITE: TLSv1.2 Handshake, length = 153
2017-10-17 14:55:38,879 INFO  [stdout] ([application]-server-thread-3) [application]-server-thread-3, READ: TLSv1 Handshake, length = 2038
2017-10-17 14:55:38,880 INFO  [stdout] ([application]-server-thread-3) *** ServerHello, TLSv1
2017-10-17 14:55:38,881 INFO  [stdout] ([application]-server-thread-3) RandomCookie:  GMT: 1491398330 bytes = { 150, 254, 235, 181, 113, 144, 110, 25, 221, 21, 250, 17, 160, 13, 69, 97, 228, 152, 63, 32, 209, 40, 157, 235, 245, 153, 134, 74 }
2017-10-17 14:55:38,882 INFO  [stdout] ([application]-server-thread-3) Session ID:  {89, 229, 239, 186, 146, 242, 123, 118, 227, 212, 229, 33, 177, 102, 106, 105, 0, 235, 87, 149, 115, 254, 5, 134, 165, 238, 96, 176, 240, 230, 244, 16}
2017-10-17 14:55:38,882 INFO  [stdout] ([application]-server-thread-3) Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA
2017-10-17 14:55:38,882 INFO  [stdout] ([application]-server-thread-3) Compression Method: 0
2017-10-17 14:55:38,882 INFO  [stdout] ([application]-server-thread-3) Extension renegotiation_info, renegotiated_connection: <empty>
2017-10-17 14:55:38,882 INFO  [stdout] ([application]-server-thread-3) ***
2017-10-17 14:55:38,882 INFO  [stdout] ([application]-server-thread-3) [application]-server-thread-3, handling exception: javax.net.ssl.SSLHandshakeException: Server chose TLSv1, but that protocol version is not enabled or not supported by the client.
2017-10-17 14:55:38,883 INFO  [stdout] ([application]-server-thread-3) [application]-server-thread-3, SEND TLSv1.2 ALERT:  fatal, description = handshake_failure
2017-10-17 14:55:38,883 INFO  [stdout] ([application]-server-thread-3) [application]-server-thread-3, WRITE: TLSv1.2 Alert, length = 2
2017-10-17 14:55:38,883 INFO  [stdout] ([application]-server-thread-3) [application]-server-thread-3, called closeSocket()
2017-10-17 14:55:38,883 INFO  [stdout] ([application]-server-thread-3) [application]-server-thread-3, IOException in getSession():  javax.net.ssl.SSLHandshakeException: Server chose TLSv1, but that protocol version is not enabled or not supported by the client.
2017-10-17 14:55:38,883 INFO  [stdout] ([application]-server-thread-3) [application]-server-thread-3, called close()
2017-10-17 14:55:38,883 INFO  [stdout] ([application]-server-thread-3) [application]-server-thread-3, called closeInternal(true)
2017-10-17 14:55:38,884 INFO  [stdout] ([application]-server-thread-3) [application]-server-thread-3, called close()
2017-10-17 14:55:38,884 INFO  [stdout] ([application]-server-thread-3) [application]-server-thread-3, called closeInternal(true)
2017-10-17 14:55:38,885 INFO  [stdout] ([application]-server-thread-3) application: [[application]-server-thread-3] 14:55:38 ERROR com.sbt.access_system.c.Request:42 - Access_system error on doGet
2017-10-17 14:55:38,885 INFO  [stdout] ([application]-server-thread-3) org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://10.111.111.111:9443/spas/rest/client-service/getUserRoles?ticket=root%2336e8e6bc47e51d3a773c0d0543a095ab15082340024201148": peer not authenticated; nested exception is javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
2017-10-17 14:55:38,885 INFO  [stdout] ([application]-server-thread-3)   at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:528) ~[spring-web-3.2.10.RELEASE.jar:3.2.10.RELEASE]

我尝试显式启用协议,但不起作用-Dhttps。协议=TLSv1,TLSv1。1,TLSv1。2,-Djdk。tls。客户协议=TLSv1,TLSv1。1,TLSv1。2.​

请告诉我该怎么办。

共有2个答案

吕高昂
2023-03-14

在我的例子中,我帮助了WebSphereSSL确认中的“SSL\uTLSV2”。

秦博延
2023-03-14

当应用程序代码覆盖TLS协议时,可能会发生此问题,请检查代码以查看您是否正在使用“TLS”设置SSL上下文,如果是,它将默认为1.0,您必须将其设置为TLSv1。2.

 类似资料:
  • 我需要有一个实时直播音频流从一个客户端到一个服务器到多个侦听器客户端。 目前,我已经从客户端录制工作和流通过套接字的音频。将io发送到服务器。服务器接收此数据,并且必须流式传输音频(也通过socket.io?)发送给希望侦听此流的客户端。它必须尽可能实时(尽量减少延迟)。 我正在使用GetUserMedia录制麦克风(浏览器兼容性在这里并不重要)。我希望客户端使用HTML5音频标签来收听流。在服务

  • 通过运行带有标志的工具,我查看了调试和跟踪日志,但我无法找到客户机何时/是否调用服务器,以及服务器实际上在寻找哪个config-data.properties文件。我有点不知道该如何进行。 下面是我的服务器: 在文件夹中,包含以下内容的文件: 我尝试了名为service-config.properties、service-config-client.properties、service-confi

  • 我试图建立一个基本的网页,允许用户在数据库的mysql表中添加一行,以便打开LED灯和使用arduino。然而,当我尝试提交表单时,页面返回500状态,mysql查询没有执行。我在我的电脑上运行linux-apache-mysql-php服务器。为什么会这样?

  • 问题内容: 是否有从客户端浏览器获取时区的可靠方法?我看到了以下链接,但我想要一个更强大的解决方案。 使用JavaScript自动检测时区 JavaScript中的时区检测 问题答案: 查看此存储库pageloom很有帮助 下载jstz.min.js并将功能添加到您的html页面 然后从您的显示代码调用此函数

  • 问题内容: 我需要知道客户的IP地址,这是我的鳕鱼 处理程序: 结果: 为什么我无法获得真正的客户IP? 问题答案: 通常,您可以用来获取正在访问Web应用程序的客户端的IP地址。但是,如果用户位于代理服务器后面或通过负载均衡器访问您的Web服务器(例如,在云托管中),则上述代码段将获取代理服务器或负载均衡器服务器的IP地址,而不是原始IP地址客户。 因此,您应该获得请求的HTTP标头“ X-Fo

  • 问题内容: 我正在使用JAX-WS,但是在检索消耗Web服务的客户端信息时遇到问题。我已经找到了如何使用JAX-RPC和Apache Tomcat Axis(而不是JAX-WS)来做到这一点。有人对此有想法吗? 问题答案: 那这个呢: