ADMC0016E: 系统无法创建 SOAP 连接器以连接到端口 16313 上的主机 xxx

Posted

技术标签:

【中文标题】ADMC0016E: 系统无法创建 SOAP 连接器以连接到端口 16313 上的主机 xxx【英文标题】:ADMC0016E: The system cannot create a SOAP connector to connect to host xxx at port 16313 【发布时间】:2017-07-13 11:32:59 【问题描述】:

在 WAS8558 上出现以下错误。 Netcool/OMNIbus WebGUI8.1 正在使用这个 WAS8558。 我在停止 WAS 并低于错误时遇到问题。 之前我已经完成了 SSL 配置并执行了下面链接中提到的步骤来启用 TLSv1.2 https://developer.ibm.com/answers/questions/206952/how-do-i-configure-websphere-application-server-ss.html

错误:

  8:46:59:065 EDT] 00000001 WsServerStop  A   ADMU3007E: Exception com.ibm.websphere.management.exception.ConnectorException: com.ibm.websphere.management.exc
eption.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host xxxxx.cap.dev.net at port 16313.
        at com.ibm.ws.management.connector.ConnectorHelper.createConnector(ConnectorHelper.java:628)
        at com.ibm.ws.management.tools.WsServerStop.runTool(WsServerStop.java:373)
        at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:271)
        at com.ibm.ws.management.tools.WsServerStop.main(WsServerStop.java:113)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
        at java.lang.reflect.Method.invoke(Method.java:620)
        at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:234)
        at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:96)
        at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:77)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
        at java.lang.reflect.Method.invoke(Method.java:620)
        at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
        at java.lang.reflect.Method.invoke(Method.java:620)
        at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
        at org.eclipse.core.launcher.Main.run(Main.java:981)
        at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:401)
        at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:164)
Caused by: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host xxxxx.cap.dev.net at port 16313.
        at com.ibm.websphere.management.AdminClientFactory.createAdminClientPrivileged(AdminClientFactory.java:635)
        at com.ibm.websphere.management.AdminClientFactory.access$000(AdminClientFactory.java:127)
        at com.ibm.websphere.management.AdminClientFactory$1.run(AdminClientFactory.java:210)
        at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
        at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:206)
        at com.ibm.ws.management.connector.ConnectorHelper.tryProtocol(ConnectorHelper.java:665)
        at com.ibm.ws.management.connector.ConnectorHelper.createConnector(ConnectorHelper.java:597)
        ... 29 more
Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:86)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:58)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:542)
        at com.ibm.websphere.management.AdminClientFactory.createAdminClientPrivileged(AdminClientFactory.java:457)
        ... 35 more
Caused by: com.ibm.websphere.management.exception.ConnectorNotAvailableException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: java.io.IOExce
ption: Exception during sslSocket.startHandshake: Received fatal alert: handshake_failure; targetException=java.lang.IllegalArgumentException: Error opening socket: 
java.io.IOException: Exception during sslSocket.startHandshake: Received fatal alert: handshake_failure]
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:429)
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient.(SOAPConnectorClient.java:228)
        ... 40 more
Caused by: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: java.io.IOException: Exception during sslSocket.startHandshake: Received fatal alert:
 handshake_failure; targetException=java.lang.IllegalArgumentException: Error opening socket: java.io.IOException: Exception during sslSocket.startHandshake: Receive
d fatal alert: handshake_failure]
        at org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.java:475)
        at org.apache.soap.rpc.Call.WASinvoke(Call.java:510)
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient$4.run(SOAPConnectorClient.java:387)
        at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
        at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:372)
        ... 41 more 

【问题讨论】:

【参考方案1】:

试试这些解决方案

1- 在浏览器上写“xxxxx.cap.dev.net:16313/soap”,然后回车检查你的问题是否与防火墙有关。

如果您收到回复,我们将确保您的问题不是防火墙问题。

2-确保证书没有过期

3- 在某些情况下,SOAP 连接器不适用于 TLSv1.2,但它适用于 v1。

4- 尝试使用 eclipse 而不是 IBM 集成设计器。

【讨论】:

2) 不,证书没有过期。不确定第 3 点和第 4 点。附加信息,我正在使用的产品是使用 WAS8.5.5.8 的 IBM 产品(netcool/omnibus webgui8.1)。我对 SOAP 不是很熟悉。在服务器端,我可以看到,端口处于侦听模式 netstat -na | grep -i 16313 tcp 0 0 0.0.0.0:16313 0.0.0.0:* 听 1) 我尝试关注xxx:16313/soap 我得到以下输出, - schemas.xmlsoap.org/soap/envelope" xmlns:xsi="w3.org/2001/XMLSchema-instance" xmlns:xsd="w3.org/2001/XMLSchema">
- - SOAP-ENV:Serverxxxxxx/soap

以上是关于ADMC0016E: 系统无法创建 SOAP 连接器以连接到端口 16313 上的主机 xxx的主要内容,如果未能解决你的问题,请参考以下文章

无法建立与基于 SOAP 的服务的连接

使用 paypal api 时无法建立 SOAP 连接

Soap调用sitemider PHP

JBOSS EAP 6.4:无法在生成的 WSDL 中的“soap:address”中使用 HTTPS 模式

webservice是基于soap协议的,在android端可以用okhttp建立连接吗

使用node-soap连接Bing Ads API