Agent Builder JMX connection using SOAP fails with ADMC0053E

Technote (troubleshooting)


Problem(Abstract)

Error ADMC0053E using Agent Builder SOAP Connection: The system cannot create a SOAP connector to connect to host.

Symptom

The following errors may be seen as a result of improper setup and configuration during a SOAP JMX Connection to the WebSphere Application Server:

- connection using Agent Builder "Test Connection" or
- during agent runtime.

Error messages seen in the KQZ_JMX_trace.log (found in ITMHOME/logs or in the Agent Builder /workspace directory), when attempting to connect to the WAS application:
...
[2012-02-15T03:12:25.857-06:00] - MIN - - MBeanClient-3 - PluginFileLoader(WebSphere Application Server version 6.1).findFile(2) - Could not open com/ibm/ws/management/connector/soap/SOAPConnectorClient$5.class, assuming it's not a file in Eclipse installation path. Cannot find common/connectors/was/connWas-1.0.jar/com/ibm/ws/management/connector/soap/SOAPConnectorClient$5.class
[2012-02-15T03:12:25.857-06:00] - WARN - - MBeanClient-3 - FileLoader(WebSphere Application Server version 6.1).findFile(2) - common/jmx-1.0.jar is not a directory or zip/jar file (looking for com/ibm/ws/management/connector/soap/SOAPConnectorClient$5.class)
[2012-02-15T03:12:25.857-06:00] - WARN - - MBeanClient-3 - FileLoader(WebSphere Application Server version 6.1).findFile(2) - common/connectors/was/connWas-1.0.jar is not a directory or zip/jar file (looking for com/ibm/ws/management/connector/soap/SOAPConnectorClient$5.class)
[2012-02-15T03:12:25.857-06:00] - MIN - - MBeanClient-3 - JarDirClassLoader(WebSphere Application Server version 6.1).findClass - defineClass com.ibm.ws.management.connector.soap.SOAPConnectorClient$5: com.ibm.ws.management.connector.soap.SOAPConnectorClient$5
[2012-02-15T03:12:25.861-06:00] - ERROR - - MBeanClient-3 - WebSphereClientProvider.connect - com.ibm.websphere.management.exception.ConnectorException: ADMC0053E: The system cannot create a SOAP connector to connect to host tivdemo at port 8881 with SOAP connector security enabled.
at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:486)
at com.ibm.tivoli.monitoring.jat.jmx.websphere.WebSphereClientProvider.connect(WebSphereClientProvider.java:133)
at com.ibm.tivoli.monitoring.jat.jmx.TivoliJMXConnectorFactory.getConnector(TivoliJMXConnectorFactory.java:173)

Cause

Improper Agent Builder or Agent Runtime Configuration

Diagnosing the problem

Verify you specified the right information for the following:
- The SOAP port WAS is listening on. The default is 8880 .

- WAS USER and PASSWORD

- SSL configuration.


Resolving the problem

The error may occur when working with Agent Builder or during Agent Runtime. To solve the problem:

- Ensure that you are able to use the WebSphere wsadmin tool on the box where the agent or Agent Builder are running.
- Also check if you are able to connect to WAS using wsadmin and SOAP, e.g.:

/opt/IBM/WebSphere/AppServer/bin/wsadmin.sh -conntype SOAP -host localhost -port 8880

The agent or Agent Builder will also be able to connect to WAS using SOAP with security enabled.

You may verify the WAS SSL Signer Exchange configuration. You need to add the signer to the trust store trust.p12. To do so, you normally need to execute wasadmin as described above, if a trust is missing you will be prompted during this tasks:
[root@tivdemo logs]# /opt/IBM/WebSphere/AppServer/bin/wsadmin.sh -conntype SOAP -host localhost -port 8880

*** SSL SIGNER EXCHANGE PROMPT ***
SSL signer from target host null is not found in trust store /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/etc/trust.p12.

Here is the signer information (verify the digest value matches what is displayed at the server): ENTER

Subject DN: CN=localhost.localdomain, O=IBM, C=US
Issuer DN: CN=localhost.localdomain, O=IBM, C=US
Serial number: 1229394092
Expires: Tue Dec 12 20:21:32 CST 2023
SHA-1 Digest: B9:9F:78:E0:D7:DD:29:58:9A:D0:59:06:94:A1:DC:73:19:5F:3C:5F
MD5 Digest: 9E:54:6F:D6:89:32:FC:AA:E3:62:6A:44:98:58:13:B3

Add signer to the trust store now? (y/n) y
A retry of the request may need to occur if the socket times out while waiting for a prompt response. If the retry is required, note that the prompt will not be redisplayed if is entered, which indicates the signer has already been added to the trust store.
WASX7209I: Connected to process "server1" on node localhostNode02 using SOAP connector; The type of process is: UnManagedProcess
WASX7029I: For help, enter: "$Help help"
wsadmin>quit
[root@tivdemo logs]#


Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Monitoring Version 6
Agent Builder

Software version:

All Versions

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Software edition:

All Editions

Reference #:

1585442

Modified date:

2013-01-21

Translate my page

Machine Translation

Content navigation