Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Matthew Hall (Matt Hall)
ASB
Lead System Architect
ASB
NZ
Matt Hall Member since 2015 25 posts
ASB
Posted: Aug 3, 2016
Last activity: Aug 31, 2016
Posted: 3 Aug 2016 0:15 EDT
Last activity: 31 Aug 2016 0:36 EDT
Closed
Solved

AES does not show the available listeners on the monitored nodes

I have AES 7.17 set up and monitoring a few different nodes all running Pega 7.19. Do i have to do anything to get AES to be able to view the listeners running on the nodes? It doesn't detect any listeners on any nodes. 

 

***Updated by moderator: Lochan to add Category***Included SR details***

 

 

To see attachments, please log in.
Data Integration
Support Case Created

Posted: 8 years ago
Posted: 3 Aug 2016 6:34 EDT
Rajiv Nistala (nistr) Senior Manager - Engineering
Pegasystems
IN

1) Are you able to see other details like requestors, agents etc. (tabs next to listeners)?

2) The monitored node for which the listeners is coming empty, are there any exceptions on that monitored node or on AES node?

To see attachments, please log in.
Posted: 8 years ago
Posted: 4 Aug 2016 1:13 EDT
Matthew Hall (Matt Hall)
ASB
Lead System Architect
ASB
NZ

Hi Rajiv

Thanks for your help. In answer to your questions

  1. I cannot get anything back for requestors or agents either.
  2. When i run the search for agents I get the error "The system cannot infer the transport information from the [unable to determine] URL." . If i search for requestors i get no results but in the lotgs i get this error "XML parsing failed com.pega.pegarules.pub.PRException: Caught exception parsing XML stream "
To see attachments, please log in.
Posted: 8 years ago
Posted: 5 Aug 2016 2:32 EDT
Abhishek Kumar (kumaa33)
Pegasystems Inc.
Senior Solutions Engineer
Pegasystems Inc.
IN

Hi Matthew,

Also can you set the log level to 'DEBUG' for the 'invokeaxis2' activity rule which will print the SOAP envelope details in PegaRULES log file, please share the pegarules logs.

And also confirm , whether the monitored node is upgraded PRPC,what is the value of below DSS settings:

Owning Ruleset: Pega-IntegrationEnginePurpose: SwitchToOldAssemblerValue

To see attachments, please log in.
Posted: 8 years ago
Posted: 18 Aug 2016 21:19 EDT
Matthew Hall (Matt Hall)
ASB
Lead System Architect
ASB
NZ

Hi Abhishek

I answered most of your question in my general post below. 

For the DSS I don't have that at all. Should I have it on 7.19?

 

To see attachments, please log in.
Posted: 8 years ago
Posted: 18 Aug 2016 21:14 EDT
Matthew Hall (Matt Hall)
ASB
Lead System Architect
ASB
NZ

Thanks for taking an interest in this one. I've attached the log file. The following entry 

"2016-08-19 12:15:46,141 [-threads-1125739482)] [  STANDARD] [                    ] [           AES:07.13] (egaAES_Data_AlertOrigin.Action) ERROR   - ExecuteGetActivityData: Connection supplied invalid. Please configure connection in node: e6cda2367b32156a7e8414ba4e0de1e1 Connection: [unable to determine] Inskey: RULE-OBJ-ACTIVITY ASB-FW-WOW-WORK SETUPATTACHMENTPAGE #20160410T231843.353 GMT ID: BLOBRead-4"

occurs when ever i try to look at the listeners.

Abhiskh i turned on the logging but it gave me no extra information. The monitored nodes are a mixture of upgraded nodes (7.16 --> 7.1.9) and some that are fresh 7.19 installs

Rajiv i had a look at your examples but the error messages look different

To see attachments, please log in.

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