Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SMA fails to instantiate WASJMXConnector due to ADMCOO16E error



SMA does not connect to node and throws exception when making local connection to the Pega 7.1.7 node.

Error Messages

com.pega.jmx.ui.util.JMXClientException: Fail to instantiate WASJMXConnector
Failed to get mbean server connection
SMA Error: Failed to create admin client
ADMCOO16E: The system cannot create a SOAP connector to connect to host <HSOT_NAME> at port 1003

Steps to Reproduce

1. Try adding a Pega 7.1.7 on SMA runing using Local connection.
2. Open the node in SMA.

Root Cause

SMA was running on HTTPS and while configuring the Remote Connection in SMA, it throws errors indicating issues related certificate handshake.


When HTTPS is used, the signer was required to be added to the local truststore. Import the SOAP SSL certificate into the JVM truststore. To overcome the issue, import the SSL certificate from the remote host into the WebSphere server instance where the SMA application is running.

For example, if "Websphere server A" is running SMA which has a node configured pointing to a PRPC instance running on "Websphere server B", you then need to do the following configuration on "Websphere server A":

1. Log in to Websphere console
2. Navigate to: Security > SSL certificate and key management > Key stores and certificates > NodeDefaultTrustStore > Signer certificates
3. Click "Retrieve from port" button.
4. In the form, include the Hostname/port of "Websphere server B" and any alias.
5. Click "Retrieve signer information" to import the certificate.

Published July 28, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us