WSO2 ESB 4.9.0:什么是错误 101500 [英] WSO2 ESB 4.9.0: what means error 101500

问题描述

在连接到服务器时，我们会收到如下错误:

<errorCode>101500</errorCode><errorMessage>发件人错误</errorMessage>

除了发件人错误"之外，有没有办法获得有关原因的更多信息?

注意:在 SSL 传输发送器中，我为 HostnameVerifier 设置了 AllowAll

<transportSender name="https" class="org.apache.synapse.transport.passthru.PassThroughHttpSSLSender"><参数名称="非阻塞"locked="false">true</参数><参数名称="http.proxyHost"locked="false">internet.proxy</parameter><参数名称="http.proxyPort"locked="false">8080</parameter><参数名称="http.nonProxyHosts"locked="false">本地主机</参数><parameter name="HostnameVerifier">AllowAll</parameter>

这里有一些更详细的日志 (wso2-esb-errors.log).请注意，有时消息会正确传递到远程服务器.远程服务器由我无法控制的客户维护.

2016-08-30 05:06:51,995 [-] [HTTPS-Sender I/O dispatcher-1] 错误 TargetHandler I/O 错误:收到致命警报:handshake_failurejavax.net.ssl.SSLException:收到致命警报:handshake_failure在 sun.security.ssl.Alerts.getSSLException(Alerts.java:208)在 sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1666)在 sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1634)在 sun.security.ssl.SSLEngineImpl.recvAlert(SSLEngineImpl.java:1800)在 sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1083)在 sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:907)在 sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)在 javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)在 org.apache.http.nio.reactor.ssl.SSLIOSession.doUnwrap(SSLIOSession.java:228)在 org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:263)在 org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:391)在 org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:119)在 org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)在 org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)在 org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)在 org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)在 org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)在 org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:586)在 java.lang.Thread.run(Thread.java:745)

解决方案

发生此错误的原因有很多.有关详细信息，请参阅下面的参考.

• 客户端和服务器使用的密码套件不兼容.这将要求客户端使用(或启用)一个密码套件服务器支持.
• 使用的 SSL 版本不兼容(服务器可能只接受 TLSv1，而客户端只能使用 SSL v3).再次，客户端可能必须确保它使用兼容版本的SSL/TLS 协议.
• 服务器证书的信任路径不完整；服务器的证书可能不受客户端信任.这通常会导致更详细的错误，但很有可能.通常情况下修复是将服务器的CA证书导入客户端的信任商店.

参考:收到致命警报:handshake_failure through SSLHandshakeExceptionp>

In a connection to a server we get errors such as:

<errorCode>101500</errorCode><errorMessage>Error in Sender</errorMessage>

Is there a way to get more information on the cause, except from "Error in Sender"?

Note: In the SSL transport sender I have set AllowAll for the HostnameVerifier

<transportSender name="https" class="org.apache.synapse.transport.passthru.PassThroughHttpSSLSender">
    <parameter name="non-blocking" locked="false">true</parameter>
    <parameter name="http.proxyHost" locked="false">internet.proxy</parameter>
    <parameter name="http.proxyPort" locked="false">8080</parameter>
    <parameter name="http.nonProxyHosts" locked="false">localhost</parameter>
    <parameter name="HostnameVerifier">AllowAll</parameter>

Here is some more in detail log (wso2-esb-errors.log). Note that sometimes the messages are delivered correctly to the remote server. The remote server is maintained by a customer on which I have no control.

2016-08-30 05:06:51,995 [-] [HTTPS-Sender I/O dispatcher-1] ERROR TargetHandler I/O error: Received fatal alert: handshake_failure
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:1666)
        at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1634)
        at sun.security.ssl.SSLEngineImpl.recvAlert(SSLEngineImpl.java:1800)
        at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1083)
        at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:907)
        at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
        at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
        at org.apache.http.nio.reactor.ssl.SSLIOSession.doUnwrap(SSLIOSession.java:228)
        at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:263)
        at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:391)
        at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:119)
        at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
        at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
        at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:586)
        at java.lang.Thread.run(Thread.java:745)

解决方案

This error can happen due to many reasons. See the reference below for more details.

• Incompatible cipher suites in use by the client and the server. This would require the client to use (or enable) a cipher suite that is supported by the server.
• Incompatible versions of SSL in use (the server might accept only TLS v1, while the client is capable of only using SSL v3). Again, the client might have to ensure that it uses a compatible version of the SSL/TLS protocol.
• Incomplete trust path for the server certificate; the server's certificate is probably not trusted by the client. This would usually result in a more verbose error, but it is quite possible. Usually the fix is to import the server's CA certificate into the client's trust store.

Reference: Received fatal alert: handshake_failure through SSLHandshakeException

这篇关于WSO2 ESB 4.9.0:什么是错误 101500的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！