Support Article
Connectivity issue between AES and monitored nodes
SA-8932
Summary
After configuring PRPC monitored nodes for AES monitoring, AES shows Alerts and Exceptions information pushed from monitored nodes, but does not show any "health" data of any monitored node.
Error Messages
2015-04-08 15:11:23,517 [fault (self-tuning)'] [OpenPortal] [ ] [ AES:07.10] ( internal.mgmt.Executable) ERROR <HOST>|<IP> <user> - Exception
com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed
at com.pegarules.generated.activity.ra_action_invokeaxis2_ab4bacc4d22ff691fd98ed821335eb56.step15_circum0(ra_action_invokeaxis2_ab4bacc4d22ff691fd98ed821335eb56.java:4048)
at com.pegarules.generated.activity.ra_action_invokeaxis2_ab4bacc4d22ff691fd98ed821335eb56.perform(ra_action_invokeaxis2_ab4bacc4d22ff691fd98ed821335eb56.java:308)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
.
.
.
Caused by: com.pega.apache.axis2.AxisFault: Transport error: 401 Error: Unauthorized
at com.pega.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:309)
.
.
.
at com.pegarules.generated.activity.ra_action_invokeaxis2_ab4bacc4d22ff691fd98ed821335eb56.step14_circum0(ra_action_invokeaxis2_ab4bacc4d22ff691fd98ed821335eb56.java:3945)
at com.pegarules.generated.activity.ra_action_invokeaxis2_ab4bacc4d22ff691fd98ed821335eb56.perform(ra_action_invokeaxis2_ab4bacc4d22ff691fd98ed821335eb56.java:291)
... 92 more
Steps to Reproduce
- Login to AES
- Navigate to Health sceen
- Expand any node bar
- Click on any link within the section
Root Cause
The root cause of this problem is defect/misconfiguration in the operating environment. Weblogic server intercepts the SOAP request from AES to PRPC node and requires basic authentication.
Resolution
This issue is resolved by making the following change to the operating environment:
Edit the config.xml file and add the following tag before the closing </security-configuration> tag of the monitored PRPC server.
<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>
Restart the AES server and restart the monitored PRPC nodes.
Published January 31, 2016 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.