个人中心
gpt4 book ai didi

java - 从 weblogic 11g 中部署为 war 的代码调用 soap 服务时出现握手错误

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

我的 soap 服务仅支持 TLSv1.2，当我通过在 main() 方法中编写客户端从本地机器调用 soap 服务时，它工作正常。我还启用了 ssl 调试，所以在本地我可以清楚地看到我是客户端正在发送*** ClientHello，TLSv1.2。

问题是当我在 weblogic 10.3.6 中将我的代码部署为 war 文件时，启用了 ssl 调试，在日志中我得到*** ClientHello，TLSv1。对于 java 中的相同客户端代码。

如果客户端是 TLSv1，它不会与服务 TLS1.2 握手吗？

在 weblogic 控制台中，我启用了 JSSE。我对需要在 weblogic 中完成的任何其他配置一无所知，或者握手错误的可能原因是什么。感谢任何类型的建议，请提供帮助。

为了更好地说明，我将我的日志粘贴到下面:

Caused by: javax.xml.ws.WebServiceException: javax.net.ssl.SSLException: Received fatal alert: handshake_failure
        at com.sun.xml.ws.transport.http.client.HttpClientTransport.readResponseCodeAndMessage(HttpClientTransport.java:218)
        at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:204)
        at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:124)
        at com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:121)
        at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:866)
        at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
        at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
        at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
        at com.sun.xml.ws.client.Stub.process(Stub.java:272)
        at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:153)
        at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:115)
        at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
        at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
        at com.sun.proxy.$Proxy791.executeProcess(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
        at com.sun.proxy.$Proxy792.executeProcess(Unknown Source)
        at aero.sita.trillium.mobility.util.ServiceHelper.swapAsset(ServiceHelper.java:4309)
        at aero.sita.trillium.mobility.service.impl.IMgmtServiceImpl.swapAssetAsJSON(IMgmtServiceImpl.java:3223)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:122)
        at com.liferay.portal.spring.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:71)
        at com.liferay.portal.dao.jdbc.aop.DynamicDataSourceTransactionInterceptor.invoke(DynamicDataSourceTransactionInterceptor.java:44)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
        at com.liferay.portal.security.pacl.PACLAdvice.invoke(PACLAdvice.java:51)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
        at com.liferay.portal.spring.aop.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:211)
        at com.sun.proxy.$Proxy691.swapAssetAsJSON(Unknown Source)
        at aero.sita.trillium.mobility.service.IMgmtServiceUtil.swapAssetAsJSON(IMgmtServiceUtil.java:698)
        ... 69 more
Caused by: javax.net.ssl.SSLException: Received fatal alert: handshake_failure
        at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
        at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1639)
        at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1607)
        at sun.security.ssl.SSLEngineImpl.recvAlert(SSLEngineImpl.java:1776)
        at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1068)
        at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:890)
        at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:764)
        at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
        at weblogic.security.SSL.jsseadapter.JaSSLEngine$4.run(JaSSLEngine.java:118)
        at weblogic.security.SSL.jsseadapter.JaSSLEngine.doAction(JaSSLEngine.java:732)
        at weblogic.security.SSL.jsseadapter.JaSSLEngine.unwrap(JaSSLEngine.java:116)
        at weblogic.socket.JSSEFilterImpl.doHandshake(JSSEFilterImpl.java:93)
        at weblogic.socket.JSSEFilterImpl.doHandshake(JSSEFilterImpl.java:59)
        at weblogic.socket.JSSEFilterImpl.write(JSSEFilterImpl.java:391)
        at weblogic.socket.JSSESocket$JSSEOutputStream.write(JSSESocket.java:78)

最佳答案

If client is TLSv1, would it not handshake with service TLS1.2 ?

在这种情况下，TLSv1 指的是 TLS 1.0。

My soap service supports TLSv1.2 only ... deploying my code as a war file in weblogic 10.3.6

您的 Weblogic 安装可能不支持 TLS 1.2。根据this documentation它在 Weblogic 11 和使用 Java 7 或更高版本时受支持。

关于java - 从 weblogic 11g 中部署为 war 的代码调用 soap 服务时出现握手错误，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/44586549/

25 4 0
文章推荐： ssl - Rundeck 背后和 SSL 代理
文章推荐： security - 通过 ssl 完成 OAuth 请求时是否需要验证随机数？
文章推荐： android - java.lang.NumberFormatException : Invalid double 异常
文章推荐： Python - 用空格格式化 file.write 字符串
太空宇宙
个人简介

我是一名优秀的程序员,十分优秀！

滴滴打车优惠券免费领取
滴滴打车优惠券
全站热门文章
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com