Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Trace open rule functionality fails with session error

SA-56806

Summary



Trace open rule functionality fails with session error.


Error Messages



[fault (self-tuning)'] [Tracer] [ ] [ ] (internal.tracer.TracerImpl) WARN  your_host|null  - Tracer: Exception while processing command

com.pega.pegarules.monitor.external.tracer.DuplicateRuleWatchException: This rule RULE-SERVICE-REST API V1!CASES #20150616T051919.151 GMT is being traced by operator your_operator from requestor HOUHOG7E69JUCDOMV9EAQ2K8K87PKDHIQ
        at com.pega.pegarules.monitor.internal.tracer.ConnectCommand.throwDuplicateRuleWatchException(ConnectCommand.java:195) ~[prprivate.jar:?]
        at com.pega.pegarules.monitor.internal.tracer.ConnectCommand.throwIfRuleIsBeingTracedInCluster(ConnectCommand.java:189) ~[prprivate.jar:?]
        at com.pega.pegarules.monitor.internal.tracer.ConnectCommand.throwIfRuleAlreadyBeingTraced(ConnectCommand.java:127) ~[prprivate.jar:?]
        at com.pega.pegarules.monitor.internal.tracer.ConnectCommand.enableClusterWideRuleWatch(ConnectCommand.java:112) ~[prprivate.jar:?]
        at com.pega.pegarules.monitor.internal.tracer.ConnectCommand.handleConnectForRuleWatch(ConnectCommand.java:68) ~[prprivate.jar:?]
        at com.pega.pegarules.monitor.internal.tracer.ConnectCommand.execute(ConnectCommand.java:47) ~[prprivate.jar:?]
        at com.pega.pegarules.monitor.internal.tracer.LocalNodeTracer.executeCommand(LocalNodeTracer.java:36) ~[prprivate.jar:?]
        at com.pega.pegarules.monitor.internal.tracer.TracerImpl.processRequest(TracerImpl.java:466) ~[prprivate.jar:?]
        at com.pega.pegarules.monitor.internal.tracer.TracerImpl.invoke(TracerImpl.java:230) ~[prprivate.jar:?]



Steps to Reproduce



Unknown


Root Cause



A defect in Pegasystems’ code or rules.


Resolution



Apply the following hotfixes and restart all the JVMs in the cluster.
  1. HFix-41101
  2. HFix-40458

Published July 23, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us