Question
Annoying Tracer timeout issue limited to 5 min only why ? PEGA 8.3.2
Hi ,
We have recently patched our platform to 8.3.2 and found a FEATURE or BUG ? while accessing tracer session. Session is being auto timeout after 5 min of usage. We cannot open page from tracer after 5 min.
As work around we are storing all tracer results and using tracer viewer to analyze it. But this is completely annoying for developers to troubleshoot something long logic flows etc.
Please let me know if any way is available to switch it OFF ? or increase this time.
Your help or comments are really appreciated.
Thx
CP
***Edited by Moderator Marissa to update Content Type from Discussion to Question; update SR Details***
Hello,
Yes , as developers we need it for sure. There are so many dependent flow cases complex business logic has to be analyzed in tracer . Its difficult to follow a workaround every time.
in case for example: you lost 1 or 2 min chatting with your team mates you might have to repeat same thing again. Simply annoying .
5 min is too less in my opinion it should be at least 15 or 30 min.
Earlier , in product this restriction was not there , its introduced in 8.3.2 patch. I am not sure why there is a need to change existing or settings /features. even they do it ,there is no way to control it? Why this was introduced is again a mystery
Thx.
Hi ChatrapalSingh,
I understand the issue. I believe you are doing this from Dev Studio. While I agree with your point that timeout can't be that less.
Can you try below steps and see if you can do a full trace for greater than the time you specified.
#1Can you take one more "New Session" of the same instance.
#2 Navigate to "Admin Studio"
#3 Navigate to Requestors>> Identify "Requestors" on your name, and pick the right session you want to trace.
#4 And start tracing from there.
And see if you still face the timeout issue.
Thanks and Regards,
Pavan Kumar Naidu.
This issue has been resolved in the 8.3.3 patch release :
https://collaborate.pega.com/discussion/pega-833-patch-release-available
We can add a DSS setting "tracer/session/timeout" that is currently defaulted to 300sec i.e 5mins
Hello,
Do you really need to trace for more than 5 minutes? The trace will be quite difficult to read with so many lines. Could you setup log messages instead to debug your process?