Support Article
call back feature in AES does not work correctly
SA-48494
Summary
In the Enterprise landing page, the call back feature does not work on selecting a system and a node. Hence, Listeners, Agents, and Nodes do not display. Additionally, data cannot be retrieved from the monitored node..
Error Messages
092 [PegaRULES-Batch-129] [STANDARD] [ ] [AES:07.14] (egaAES_Data_AlertOrigin.Action) ERROR - ExecuteGetActivityData: Error. Cluster: RSM-PROD Node: 12b1929305267868e11636d84a1b546f Connection: http://your_server:your_port/prweb/PRSOAPServlet InsKey: RULE-OBJ-ACTIVITY RULE-OBJ-LISTVIEW SORTCOLUMN #20130919T000540.578 GMT ID: HTMLStream-901 Msg: ** SOAP service failed
099 [PegaRULES-Batch-129] [STANDARD] [ ] [AES:07.14] (egaAES_Data_AlertOrigin.Action) ERROR - Rule data lookup failed for: HTMLStream-901 -- please verify that PegaAESRemote application has been appropriately installed and configured on the monitored system.
105 [PegaRULES-Batch-129] [STANDARD] [ ] [AES:07.14] (egaAES_Data_AlertOrigin.Action) INFO - ExecuteGetActivityData: Failed node validation: NodeID: Status:
170 [PegaRULES-Batch-129] [STANDARD] [ ] [AES:07.14] ( internal.mgmt.Executable) ERROR Rule-Connect-SOAP.PegaAES-Data-AlertOrigin.GetActivityData - Exception
Steps to Reproduce
Not Applicable
Root Cause
A defect in Pegasystems’ code or rules.
During auto discovery on the monitored nodes, the correct context root was not sent to the AES server.
For example:
924 GMT*8*PEGA0008*0*0*a7602086ebd7db714b9393f3a80e14d3*NA*NA*B364E851DA8A01C5275228D2D3D143EFA*none*PegaSample*null*0876e1f56df2c86fe5070a8210b0a152*N*0*A5E7C7133DEE986CE06A9B0E6E46A4528*9*LKELLJ3W7US*STANDARD*com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup*NA*(License Daemon)**NA*NA*NA*NA*NA*NA*NA*PegaRULES engine successfully started. TimeZone: America/New_York AESPerfStatMode: PUSH Server: your_server System: pega Description: a7602086ebd7db714b9393f3a80e14d3 Production Level : 2 URL: http://your_server:your_port/prweb/PRSOAPServlet*
This context root was included as defined in the deployment.
924 GMT*8*PEGA0008*0*0*a7602086ebd7db714b9393f3a80e14d3*NA*NA*B364E851DA8A01C5275228D2D3D143EFA*none*PegaSample*null*0876e1f56df2c86fe5070a8210b0a152*N*0*A5E7C7133DEE986CE06A9B0E6E46A4528*9*LKELLJ3W7US*STANDARD*com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup*NA*(License Daemon)**NA*NA*NA*NA*NA*NA*NA*PegaRULES engine successfully started. TimeZone: America/New_York AESPerfStatMode: PUSH Server: your_serverSystem: pega Description: a7602086ebd7db714b9393f3a80e14d3 Production Level : 2 URL: http://your_server:your_port/UAT4/PRSOAPServlet*
The context root 'prweb' was not available on the server. However, when the monitored node was started the context root was sent. The Pega platform performed an auto discovery of its URL and could not retrieve the correct URL occasionally.
Resolution
- Apply HFix-33866.
- Perform the following local-change:
Change the New Connection String to include the correct context root (as in the below image). Use the PegaAES-Data-Node content on the AES Server to make the change.
Tags:
Published April 2, 2018 - 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.