Ghost requestor not allowing to trace
Hi Guys!
We were experiencing this for a long time, now we had some time to take a deeper look at the issue.
Sometimes the tracer session gets stuck. By this I mean that despite you have closed the tracer window, the system thinks your requestor is still tracing. Usually, a terminate trace or a logoff login solves this irritating issue.
Today we have experienced a this on a higher level:
The tracer cannot be started because an other requestor traces it, but that requestor does not even exist.
We know that it does not exist because it is not present on the requestor list, and we got the following error while trying to kick it programmatically:
Invalid value for requestor parameter: *****
Using the following code
((PegaAPI)tools).getSystemOperationsProvider().getRequestorManagementAPI().terminateRequestor("a3dfe82086b5f811c5e5b423551fda2b", "H017F9679D140C8081FDE7A9DDFFB4448")
See pictures attached.
Hi Guys!
We were experiencing this for a long time, now we had some time to take a deeper look at the issue.
Sometimes the tracer session gets stuck. By this I mean that despite you have closed the tracer window, the system thinks your requestor is still tracing. Usually, a terminate trace or a logoff login solves this irritating issue.
Today we have experienced a this on a higher level:
The tracer cannot be started because an other requestor traces it, but that requestor does not even exist.
We know that it does not exist because it is not present on the requestor list, and we got the following error while trying to kick it programmatically:
Invalid value for requestor parameter: *****
Using the following code
((PegaAPI)tools).getSystemOperationsProvider().getRequestorManagementAPI().terminateRequestor("a3dfe82086b5f811c5e5b423551fda2b", "H017F9679D140C8081FDE7A9DDFFB4448")
See pictures attached.
Saltech Consulting
HU
Pega version 7.3. I did not save the logs.
But I think you can pretty easily reproduce it when fiddling with tracing a service.
(I will also try to come up with some clean repro, but do not have much time for it at the moment)
Saltech Consulting
HU
Hi SudhakarReddy,
I have run into the issue again. I have checked the logs, could not find anything specific to this.
The symptom is the same: the system thinks the requestor is tracing that listener, but in reality, it is not.
When trying to stop the trace it says that the tracer was stopped, but the system still thinks it is still tracing.
I think this one can be again only solved by a full restart.