Question

1
Replies
23
Views
MichaelH0368 Member since 2018 1 post
Bitmarck
Posted: March 3, 2020
Last activity: March 3, 2020

Is there any Information in the PEGA-AES to prevent a campaign Crash

Hi all,

We had a campaign Crash with staus=failed and no more Information. The only thing that we found in the logs was that below.

We are working here with the "PEGA AES (Automatic Event Service)" tool.

My question is: is it possible to note this behavior earlier in the "PEGA-AES" ? Is there any more Information in the PEGA-AES to prevent such a campaign Crash?

Log - Information: "event=ASSIGNED, assignedNode=l0101vw3268out2, originator=DataFlowServiceImpl, reason=Detected active run with unreachable nodes. Applying node fail policy for nodes [l0101vw3257out3, l0101vw3258out4, l0101vw3267out1], senderNodeId=l0101vw3268out2, timestamp=1582263905450, currentCluster=[MemberInfo{uuid=8e813e92-dd76-450b-9785-370ce576a343, prpcId=l0101vw3257out3, state=UNREACHABLE, errorMessage=Unable to reach the node due to an exception}, MemberInfo{uuid=df7f5a93-e618-4a2f-825d-36893b85616b, prpcId=l0101vw3258out4, state=UNREACHABLE, errorMessage=Unable to reach the node due to an exception}, MemberInfo{address=10.2.81.250, uuid=5a414d95-8e75-4935-a859-2f61549eca4c, prpcId=l0101vw3259adm, state=NORMAL}, MemberInfo{uuid=9d8a27b4-05d3-4d9d-b692-37faa120b6be, prpcId=l0101vw3267out1, state=UNREACHABLE, errorMessage=Unable to reach the node due to an exception}, MemberInfo{address=10.2.82.146, uuid=61a805d0-d3d5-41c3-b05f-790e0d3fe308, prpcId=l0101vw3268out2, state=NORMAL}, MemberInfo{address=10.2.82.147, uuid=6b1423d8-08d6-4e5f-914c-5e66efb5a790, prpcId=l0101vw3269vbd, state=NORMAL}]}

2020-02-21 06:49:39,694 [aab.cached.thread-11] [ STANDARD] [  

thx

 

***Edited by Moderator Marissa to update SR Details***

Pega Marketing 8.1 Low-Code App Development Dev/Designer Studio Healthcare and Life Sciences System Architect SR Exists
Share this page LinkedIn