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

 Nagaraj Ponnurangam (NagarajP0101)
ING Belgium SA NV

ING Belgium SA NV
BE
NagarajP0101 Member since 2017 54 posts
ING Belgium SA NV
Posted: Jan 2, 2018
Last activity: Jan 3, 2018
Posted: 2 Jan 2018 8:11 EST
Last activity: 3 Jan 2018 11:22 EST
Closed
Solved

Standard Agent is not running in Production

We have configured agent of type 'standard' to process queue entries and interval is 10 secs. sometimes its not running even if the queue contains entries.

We verified the last run of the standard agent and its today morning. We din find any errors in the log too. we can't trace this agent as tracer and SMA is disabled because of client specific security reasons.

I have referred couple of posts related to this and ensured the following

1.AccessGroup and RS is correct

2.Agent activity class and queue class is same

3.activity belongs to correct RS

4.Checked Bypass activity authentication in Agents Security tab

5.There are no broken queue items.

Kindly advise what could be the issue here .

To see attachments, please log in.
Low-Code App Development

Accepted Solution

Posted: 6 years ago
Posted: 3 Jan 2018 11:18 EST
Ujjwal Kumar Shukla (UjjwalShukla_GCS)
PEGA
Senior Manager, Technical Support
Pegasystems Inc.
IN

Hi Nagaraj,

In case of tracer and SMA not an option, could you please use PAL(Performance Analyser) to perform DB trace.
It would give you the stack trace similar to that of tracer.

If option permits you may put logger steps in Activity to see if agent runs completely.

Thanks,
Ujjwal

To see attachments, please log in.
Posted: 6 years ago
Posted: 2 Jan 2018 9:24 EST
Laurence Brannigan (LaurenceB_GCS)
PEGA
Senior Software Solutions Engineer
PEG
GB

I think investigation will be drastically hampered if you have no error in the log and you don't have access to  tracer (and SMA).

How have you established that it isn't running? Was it originally observed that expected actions weren't happening and this led you to look into the relevant queue table to check for entries which should have processed (pyMinimumDataTimeForProcessing is in the past)?

Or are you using one of the later releases where you can examine the agent status from Designer Studio (System > Operations > Agent Management)?

To see attachments, please log in.
Posted: 6 years ago
Posted: 2 Jan 2018 9:41 EST
Nagaraj Ponnurangam (NagarajP0101)
ING Belgium SA NV

ING Belgium SA NV
BE

we could see agent is running(System > Operations > Agent Management) and its of status 'scheduled' . 

I have referred below post in which they have changed the mode of the agent.

https://community.pega.com/support/support-articles/standard-agent-not-working

But i din get the reason for the change and what is the problem with 'Standard' mode. Am i missing something from the post?

To see attachments, please log in.

Accepted Solution

Posted: 6 years ago
Posted: 3 Jan 2018 11:18 EST
Ujjwal Kumar Shukla (UjjwalShukla_GCS)
PEGA
Senior Manager, Technical Support
Pegasystems Inc.
IN

Hi Nagaraj,

In case of tracer and SMA not an option, could you please use PAL(Performance Analyser) to perform DB trace.
It would give you the stack trace similar to that of tracer.

If option permits you may put logger steps in Activity to see if agent runs completely.

Thanks,
Ujjwal

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