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

Unable to connect to SMA node due to LinkageError



User is unable to connect to a Pega node (remote connection) from System Management Application (SMA) due to a java.lang.LinkageError. 
WebSphere [IBMJAVA71 cf091608.04]Platform [ND cf091608.05]
Host Operating System is AIX, version 7.1
Java version = 1.7.0, Java Runtime Version = pap6470_27sr3fp30-20160112_01 (SR3 FP30), Java Compiler = j9jit27, Java VM name = IBM J9 VM


Error Messages

[6/17/16 10:29:36:702 EDT] 0001957d Dispatcher E org.apache.struts2.dispatcher.Dispatcher error Exception occurred during processing request: null

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Caused by: java.lang.LinkageError: com/ibm/websphere/management/AdminClient.queryNames(Ljavax/management/ObjectName;Ljavax/management/QueryExp;)Ljava/util/Set;

at com.pega.jmx.connection.managenodes.WASRemoteMBeanServerConnection.queryNames(

Steps to Reproduce

Setup a remote connection in SMA and attempt to connect to it.

Root Cause

A third-party product issue. Automated Websphere deployment script was in use for SMA app deployment instead of the manual deployment recommended in the install guide.


Make the following change to the operating environment: Deploy SMA using Websphere console, as documented in the install guide.

Refer to the section with title : "Deploy the System Management and Online Help Applications "

Published August 17, 2016 - Updated October 8, 2020

Was this useful?

100% 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