Getting frequent exception "Trying to stop a timer (in stopAndStart), which has not been started on this Requestor"
We are getting following exceptions frequently in log file in random application functional area. Does not look to have a coding issue as it occurs any application area. If anyone have any experience on such exception earlier and have any fix recommendation, would be great help. The product stack we have Pega 7.1.7 , Pega NBAM 7.12.
--------------------------
Trying to stop a timer (in stopAndStart), which has not been started on this Requestor. Stop Timer: pxDeclarativePageLoadElapsed/pxDeclarativePageLoadCPU Stop Count: 1 Start Timer: pxOtherIOElapsed/pxOtherIOCPU {java.lang.Exception: com.pega.pegarules.monitor.internal.pal.PALDurationImpl.stopAndStart (PALDurationImpl.java:230)
com.pega.pegarules.monitor.internal.pal.PALDurationImpl._meStartRecursiveTimer (PALDurationImpl.java:284)
com.pega.pegarules.monitor.internal.pal.PALDurationImpl.startRecursiveTiming (PALDurationImpl.java:351)
***Moderator Edit: Vidyaranjan | Updated Categories***
**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.
Pegasystems Inc.
US
Although harmless in nature, it points to a race condition issue between requestors. Do the occurrences always
reference the same pxDeclarativePageLoadElapsed/pxDeclarativePageLoadCPU
and pxOtherIOElapsed/pxOtherIOCPU timers?
Capgemini
IN
I see below 2 log variation
1. Attempting to stop timer pxDeclarativePageLoadElapsed/pxDeclarativePageLoadCPU . Timer was not at the top of the stack. Top: pxConnectClientInitElapsed/pxConnectClientInitCPU
2. Trying to stop a timer (in stopAndStart), which has not been started on this Requestor. Stop Timer: pxDeclarativePageLoadElapsed/pxDeclarativePageLoadCPU Stop Count: 1 Start Timer: pxOtherIOElapsed/pxOtherIOCPU
Any solution recommendation? Help is much appreciated.
Pegasystems Inc.
IN
Capgemini
IN
Hi All,
It appears to be product issue. We had logged SR with Pega and finally arrived that this is something can't be even fixed under Hotfix. I believe Pega GCS has taken this to fix in any future pega version but no idea which version it would be. However there is an alternate solution to avoid this error. Do not implement SOAP connect call on back of Data Page. Use earlier conventional method like calling from an activity and call activity from flow or UI button event etc.
We noticed this error to be appearing when called on back of data page. But it does not come when we directly call from activity.