Question
Vodafone
IN
Last activity: 19 May 2020 9:17 EDT
Pega agent is hanged - stuck thread observed in server log
Our application uses Pega 7.3.1 version and our requirement is run the agent which consume AWS SQS records using a shell script through which email tracking records would be populated in weblogic queue. JMS listener in pega will listen to that queue for processing.
Note : Agent runs for every 30s and will fetch max 250 records(Shell script can run for 10 mins max to process 50k records appx)
During this process, thread got stucked and agent is not processing any records. PFA, stack trace of stuck thread.
Refered pdn article https://community.pega.com/support/support-articles/pega-agent-getting-hung-and-failed-do-its-job for which the problem is RUF.
Is there any existing issue similar to this? any pointers how this can be avoided
***Edited by Moderator Marissa to update Product Version and Platform Capability Tags***
Proximus
BE
Hello,
I'm not using same background technologies but the concept is the same.
Your agent will trigger an activity which will processes 250 records.
- When you manuallty run this activity, is it working fine?
- Can you add debug line so that you can see which item is being processed, and when it's completed (plus any useful steps)?
- isn't there any DB lock at the time it stops processing?
- is it blocking at first run of the activity or at second run?
- if you set max records to 1, is it blocking the same way?
- Does your activity properly finish and well returns completed status?
If you can have your activity properly working when manually triggered, then it will end of debugging agent issues only and not agents & business functionalities.
Regards
Anthony