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

System Management Application URL does not work

SA-81531

Summary



System Management Application (SMA) URL does not work. Post a JVM restart, the SMA works for a day and an error message displays.


Error Messages



com.pega.jmx.ui.util.JMXClientException: Exception getting MBean Server connection. Fail to instantiate WASJMXConnector 
Failed to get mbean server connection 
SMA ERROR: Failed to create admin client 
ADMC0016E: The system cannot create a SOAP connector to connect to host lwsprib00001049 at port 28880.


Stack Trace: 

com.pega.jmx.ui.util.JMXClientException: Exception getting MBean Server connection. Fail to instantiate WASJMXConnector Failed to get mbean server connection SMA ERROR: Failed to create admin client ADMC0016E: The system cannot create a SOAP connector to connect to host lwsprib00001049 at port 28880. at com.pega.jmx.ui.util.JMXClientException.wrap(JMXClientException.java:49) at com.pega.jmx.ui.action.AuthenticateAction.execute(AuthenticateAction.java:347) at com.pega.jmx.ui.action.AuthenticateAction.executeWithoutValidation(AuthenticateAction.java:87) at sun.reflect.GeneratedMethodAccessor162.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:507) at ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:892) at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:1537) at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:68) at com.opensymphony.xwork2.ognl.accessor.XWorkMethodAccessor.callMethodWithDebugInfo(XWorkMethodAccessor.

Error in the Application server logs:

SSLC0008E: Unable to initialize SSL connection.  Unauthorized access was denied or security settings have expired. Exception is javax.net.ssl.SSLHandshakeException: Client requested protocol TLSv1 not enabled or not supported


Steps to Reproduce



Access the nodes from the SMA.


Root Cause



This issue occurred when connecting to a remote node. Local connections are accessible.


Resolution



Pega does not implement TLS itself and relies on the underlying JVM to facilitate SSL/TLS/HTTPs.

WebSphere Application Server (WAS) vendor IBM recommended the modification of the WAS SSL protocol to SSL_TLSv2 which supports TLSv1, TLSv1.1 and TLSv1.2.

Published August 15, 2019 - 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