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"><参数名称="non-blocking"已锁定="false"> true</parameter><参数名称="http.proxyHost"锁定="false"> internet.proxy</参数><参数名称="http.proxyPort"已锁定="false"> 8080</parameter>< parameter name ="http.nonProxyHosts"已锁定="false"> localhost</parameter>< 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.可读(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证书导入到客户端的信任中商店.

参考:收到的致命警报:通过SSLHandshakeException的handshake_failure

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屋！