Skip to main content
Contact a Moderator

Question

5
Replies
493
Views
 Jagannath Rajagopalan (JagannathR8869)
DXC Technology

DXC Technology
BE
JagannathR8869 Member since 2016 43 posts
DXC Technology
Posted: February 1, 2018
Last activity: April 10, 2018
Posted: 1 Feb 2018 5:33 EST
Last activity: 10 Apr 2018 15:43 EDT
Closed

SMA connection error for Pega 7.3 application

Dears,


We are using a new Pega 7.3 for one application and the rest old ones are Pega 7.1.8


But we use a common SMA URI for both.


The applications in 7.1.8 are working fine when accessed by SMA. But the 7.3 one seems to be giving the below error.


In the DSS of the app, we have configured the SystemManagementURI to the same URI as other apps in 7.1.8


Also in DSS, the SearchSOAPURI is configured : http://xxx.web.bc:35282/SWW/PRSOAPServlet


In SMA, we have configured the primary & diagnostic url as http://xxx.web.bc:35282/SWW/PRServlet & DiagnosticData respectively.


Is there something extra which needs to be done for SMA in case of Pega 7.3 apps or am i missing something ?




MSG:


com.pega.jmx.ui.util.JMXClientException: 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 http://xxx.web.bc at port 35282.

Stack Trace:

Show More

Dears,

We are using a new Pega 7.3 for one application and the rest old ones are Pega 7.1.8

But we use a common SMA URI for both.

The applications in 7.1.8 are working fine when accessed by SMA. But the 7.3 one seems to be giving the below error.

In the DSS of the app, we have configured the SystemManagementURI to the same URI as other apps in 7.1.8

Also in DSS, the SearchSOAPURI is configured : http://xxx.web.bc:35282/SWW/PRSOAPServlet

In SMA, we have configured the primary & diagnostic url as http://xxx.web.bc:35282/SWW/PRServlet & DiagnosticData respectively.

Is there something extra which needs to be done for SMA in case of Pega 7.3 apps or am i missing something ?

MSG:

com.pega.jmx.ui.util.JMXClientException: 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 http://xxx.web.bc at port 35282.

Stack Trace:

				    com.pega.jmx.ui.util.JMXClientException: 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 http://xxx.web.bc at port 35282.
	at com.pega.jmx.ui.util.JMXClientException.wrap(JMXClientException.java:49)
	at com.pega.jmx.ui.action.AuthenticateAction.execute(AuthenticateAction.java:346)
	at com.pega.jmx.ui.action.AuthenticateAction.executeWithoutValidation(AuthenticateAction.java:86)
	at sun.reflect.GeneratedMethodAccessor160.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
	at java.lang.reflect.Method.invoke(Method.java:611)
	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.java:117)
	at com.opensymphony.xwork2.ognl.accessor.XWorkMethodAccessor.callMethod(XWorkMethodAccessor.java:108)
	at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:1613)
	at ognl.ASTMethod.getValueBody(ASTMethod.java:91)
	at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:212)
	at ognl.SimpleNode.getValue(SimpleNode.java:258)
	at ognl.Ognl.getValue(Ognl.java:467)
	at ognl.Ognl.getValue(Ognl.java:431)

Show Less
Low-Code App Development System Administration Installation and Deployment
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 3 years ago
Posted: 1 Feb 2018 23:05 EST
Manjunatha Anantharaju (Manju_GCS)
PEGA
Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hi ,


Could you please let us know , in which version you have configured SMA.


If possible share the screen shot of configuration.


And also,


When running System Management Application on Websphere, the Node should have the following configuration:


 


1) Configue SMA with Remote connection

Show More

Hi ,


Could you please let us know , in which version you have configured SMA.


If possible share the screen shot of configuration.


And also,


When running System Management Application on Websphere, the Node should have the following configuration:


 


1) Configue SMA with Remote connection


2) Specify the Host Name


3) Specify the port number which should be the SOAP_CONNECTOR_ADDRESS.


4) The credentials should be the same as Websphere Administrator's credentials.



Show Less
Posted: 3 years ago
Posted: 5 Feb 2018 9:57 EST
Jagannath Rajagopalan (JagannathR8869)
DXC Technology

DXC Technology
BE

Thanks for your response.


The SMA is deployed using the prsysmgmt.ear of Pega 6 and is being used currently with Pega 7.1.8


The SMA is indeed configured with Remote connection, host name, port of the soap connector. 


The new application running on Pega 7.3 is using WAS  8.5 whereas the rest of the applications running 7.1.8 are on WAS 8


Hope this helps.


 


regards,


Jagan


 
Posted: 3 years ago
Posted: 10 Apr 2018 15:43 EDT
Ganesh Iyer (GaneshI9)
American Express

American Express
US

We are using the below service URL as suggested elsewhere on PDN. It is working with Jboss 6.x but not with Jboss 7.x 


service:jmx:remoting-jmx://{hostname}:{port}


Below is the error


com.pega.jmx.ui.util.JMXClientException: No MBeans found for the node 

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

Pega Collaboration Center 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