Question
Plexus Tech
ES
Last activity: 6 Jul 2020 9:05 EDT
Product Pega Marketing v8.3.0. Error in Trace a Service from Package PegaMKTContainer
Hi,
I try to trace the service "PegaMKTContainer/V2/CaptureResponse" and when I run "Action > Tracer" always outputs this message:
Tracer session error: This rule RULE-SERVICE-REST PEGAMKTCONTAINER V2!CAPTURERESPONSE33A9EDDC81205172FECA77EDCCD81BB1 #20180514T183221.085 GMT is being traced by operator [email protected] from requestor H6MIOISO7B0JU5PVN9YZNNMW36Q2406SFA - Please restart tracer.
¿How can I restart the tracer of the requestor that has this rule locked?, in Admin Studio the requestor session does not appear in order to run: terminate tracer.
¿Does anyone know how I can solve this problem? thanks a lot.
***Edited by Moderator Kayla to update Platform Capability tags****
***Edited by Moderator Marissa to update General to Product; update Support Case Details***
Accepted Solution
Updated: 25 Jun 2020 14:15 EDT
Plexus Tech
ES
Good morning, I share the solution received from Pega's support team (Marije_GCS)
- Support Case ID: INC-130868 Error Tracer Tool for requestor
- Type of Incident: Product
- Resolution type: Solution
- Root cause: Pegasystems Bug
- Root cause description: A defect in Pegasystems’ code or rules Repaired Tracer use with Chrome After running Tracer while using Chrome, closing it and trying to run another resulted in an error indicating "Cannot Launch multiple tracer sessions for a requestor". This was identified as a bug with Chrome Versions greater than 70 and was caused by Chrome deprecating the use of sync XHR on page dismissal, and has been resolved by modifying the system to use a beacon API instead. In 8.3.3 the issue was fixed under BUG-546597 and BUG-550989.
- Solution type: New Release
- Solution description: Install or upgrade to the new release 8.3.3
thanks everyone.
Miguel.
Updated: 25 Jun 2020 0:40 EDT
Plexus Tech
ES
Good morning, I share the solution received from Pega's support team (@Marije_GCS)
Type of Incident: Product Resolution type: Solution Root cause: Pegasystems Bug Root cause description: A defect in Pegasystems’ code or rules Repaired Tracer use with Chrome After running Tracer while using Chrome, closing it and trying to run another resulted in an error indicating "Cannot Launch multiple tracer sessions for a requestor". This was identified as a bug with Chrome Versions greater than 70 and was caused by Chrome deprecating the use of sync XHR on page dismissal, and has been resolved by modifying the system to use a beacon API instead. In 8.3.3 the issue was fixed under BUG-546597 and BUG-550989, Solution type: New Release Solution description: Install or upgrade to the new release 8.3.3
thanks everyone. Miguel.
Pegasystems Inc.
US
Hi Miguel!
Could you share your Support Case ID so that we can update your post?
Thanks so much!
Marissa | Senior Moderator | Pega Collaboration Center
Accepted Solution
Updated: 25 Jun 2020 14:15 EDT
Plexus Tech
ES
Good morning, I share the solution received from Pega's support team (Marije_GCS)
- Support Case ID: INC-130868 Error Tracer Tool for requestor
- Type of Incident: Product
- Resolution type: Solution
- Root cause: Pegasystems Bug
- Root cause description: A defect in Pegasystems’ code or rules Repaired Tracer use with Chrome After running Tracer while using Chrome, closing it and trying to run another resulted in an error indicating "Cannot Launch multiple tracer sessions for a requestor". This was identified as a bug with Chrome Versions greater than 70 and was caused by Chrome deprecating the use of sync XHR on page dismissal, and has been resolved by modifying the system to use a beacon API instead. In 8.3.3 the issue was fixed under BUG-546597 and BUG-550989.
- Solution type: New Release
- Solution description: Install or upgrade to the new release 8.3.3
thanks everyone.
Miguel.