Support Article
Tracer error when event is traced with PRPC 6.3 SP1
SA-23693
Summary
Tracer error received whenever user tries to trace any event. Within a few minutes of running it throws the below error message.
Error Messages
"Please restart tracer because tracer session error: null"
Steps to Reproduce
Run the tracer.
Root Cause
The PRPC system setting initilization/persistrequestor was set to AtInteractionEnd.
<env name="initialization/persistrequestor" value="AtInteractionEnd" />
When persistreqestor is set to AtInteractionEnd browser requestors passivate each time the passivation daemon runs.
This is because the setting is used in environments where sticky routing is not set.
So any node in a cluster of PRPC system could service requests. Leaving these requestors active on a Node is not required.
This causes problems with running tracer when the requestor is passivated. When tracer is running it's sending HTTP requests to read data provided by the requestor object and not a HTTP request that would keep the requestor active. When the requestor passivates is when the error occurs in tracer.
Note: Always use sticky sessions when possible. Using AtInteractionEnd is very performance expensive and will slow down your application.
Resolution
Change the setting value to OnTimeout:
<env name="initialization/persistrequestor" value="onTimeout" />
Published May 25, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.