Discussion

Tracing an Agent Queue

I want to trace all of the agent activities of all the agents in an agent queue. I tried the the METHOD 1 mentioned in http://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V53/howto/howto2/howtodebugagents.asp
But i get following error when I use the requestor Management

"Requestor does not exist, it may have been terminated: B828747B52DCE9FD0BF063B236B567222 "

hence I am not able to trace my agent activities.
Can anyone help in this?

Thanks in advance

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Comments

Keep up to date on this post and subscribe to comments

June 16, 2010 - 10:52am

Once agent requestor is created under Requestor Management and stating that waiting upto 60 seconds... if you click that moment... you could able the tracing an agent activity.

You need to be quite reactive... please try 3 -4 times... you will see the desired result.

June 16, 2010 - 11:49pm

Thanks for the help Krishna, but i tried again .. I tried to refresh quite a lot of times, but my requestor just didn't appear in the requestor management.
However, when i went back to Agent Management, I saw following exception
"Exception at 20100616T142346.265 GMT: com.pega.pegarules.pub.clipboard.InvalidReferenceException: The reference Primary is not valid. Reason: this step page does not exist and cannot be shown at com.pegarules.generated.activity.ra_action_aig_aus_policy_booking_etravel_processbookpolicywo_bce14c27a632c7fd9895473d6b47cd0a.step3_circum0(ra_action_aig_aus_policy_booking_etravel_processbookpolicywo_bce14c27a632c7fd9895473d6b47cd0a.java:389) at ... "
and there is a huge stack trace below this.

Does this mean that my requestor is not getting created?
I tried unit testing the activities the agent is calling and they individually are working fine.

quote:


Originally posted by pega_krishna

Once agent requestor is created under Requestor Management and stating that waiting upto 60 seconds... if you click that moment... you could able the tracing an agent activity.

You need to be quite reactive... please try 3 -4 times... you will see the desired result.


June 17, 2010 - 12:06am

However, I did find a requestor in my userID ... Not sure whether is it the same one that I am looking for. In PDN, I found out that following phrase would appear in the Last input column "Waiting up to 60 seconds for Tracer connection... " ... It did not in my case.

When I tried to trace the requestor on my name ... it opened a pop-up to a non-existent link.

http://prtd3r7cvxtra01:9082/prweb/PRServlet?pyActivity=Data-TRACERSettings.TracerOptionsAvailable&ConnectionID=H9FE6B4C596DD9455E3696744CC2B4F57

the server "prtd3r7cvxtra01" doesn't exist on our server. I tried to ping it.

My questions now are ...
1) Am I tracing the right requestor?
If yes, then ..
2) How does this link of tracer configured? and ..
3) Why is it different from our existing Pega link?

August 3, 2010 - 5:17pm

quote:


Originally posted by INAMDARN

However, I did find a requestor in my userID ... Not sure whether is it the same one that I am looking for. In PDN, I found out that following phrase would appear in the Last input column "Waiting up to 60 seconds for Tracer connection... " ... It did not in my case.

When I tried to trace the requestor on my name ... it opened a pop-up to a non-existent link.

http://prtd3r7cvxtra01:9082/prweb/PRServlet?pyActivity=Data-TRACERSettings.TracerOptionsAvailable&ConnectionID=H9FE6B4C596DD9455E3696744CC2B4F57

the server "prtd3r7cvxtra01" doesn't exist on our server. I tried to ping it.

My questions now are ...
1) Am I tracing the right requestor?
If yes, then ..
2) How does this link of tracer configured? and ..
3) Why is it different from our existing Pega link?


My Basic Understanding and Usage of tracing an Agent, I follow these steps;

1. Open the agent Management
2. Select the Agent
3. Stop It Once
4. Delay it when stopped (Do it 2-3 Times)
5. Start it
6. "Pega-IntSvcs #0: Waiting up to 60 seconds for Tracer connection" I saw this when i started
7. Selected the Agent Queue and Clicked Tracer.
8. Got the trace working..

Hope this helps you!

Thanks!
7.

August 4, 2010 - 10:18am

Hi INAMDARN,

Recently, we also faced the same issue when tracing an agent:
"Requestor does not exist, it may have been terminated: B828747B52DCE9FD0BF063B236B567222".
We debugged and found out that the Agent was configured as Standard Mode, which expects Queue items in an agent queue. These items should be placed using a prior activity with a call to Queue-For-Agent method. This kind of a setup is for task-driven agents, which work on specific work items. Else, you have to go for Schedule-driven agents making the agent as "Advanced" Mode. I think this is the same reason for the other error you are getting: "Primary page not available". You have place work items in the queue for the agent to work on.

Hope This Helps,
Arjun

June 11, 2015 - 8:27am
 
ASHWIN16NOV, thank you!

 

>> 3. Stop It Once

>> 4. Delay it when stopped

 

This solved our issue. Delay does not apply to a running agent. We MUST stop it before the delaying, otherwise nothing happens. It is documented nowhere unfortunately!