search cancel

After enabling wesb.pbd and wps.pbd, getting error: "Can't proceed because there are conflicting tracer parameters for MedPrimBlamedFaultTracer, BOMapBlamedFaultTracer. Please restart with valid directives."

book

Article ID: 42077

calendar_today

Updated On:

Products

CA Application Performance Management Agent (APM / Wily / Introscope) INTROSCOPE

Issue/Introduction

Introduction: 

 

  You can enable monitoring for WebSphere Process Server. This includes monitoring capability for WebSphere Enterprise Service Bus, when installing the Introscope agent and selecting WebSphere as the application server or manually after installing the agent. If you selected the SOA extension for WebSphere Process Server and WESB when installing the agent, the files for monitoring both WebSphere Process Server and WebSphere Enterprise Service Bus are available in the <agent_home> directory. After installing the agent, you must manually enable the SOA extension for either WebSphere Process Server or WebSphere Enterprise Service Bus by configuring the agent profile.

wps.pbd  - Monitoring of all WebSphere Process Server components, including WebSphere Enterprise Service Bus.

wesb.pbd - Monitoring only WebSphere Enterprise Service Bus components in a standalone WESB environment.

 

Question: 

I deployed the files wesb.pbd and wps.pbd and the log file shows this error message:

 

[ERROR] [IntroscopeAgent.Agent] Introscope AutoProbe will not run because the provided directives files are not valid: Can't proceed because there are conflicting tracer parameters for MedPrimBlamedFaultTracer, BOMapBlamedFaultTracer.  Please restart with valid directives.

 

I commented out the lines that contain MedPrimBlamedFaultTracer and BOMapBlamedFaultTracer in the files wesb.pbd and wps.pbd, and it works, but the problem is that the dashboards are not showing all of the information.

 

How can avoid this error and include both the wesb and wps pbd files?

 

Environment:  

APM Websphere Agent

 

Answer: 

Both wps.pbd and wesb.pbd conflict if running together because WPS extends WESB and already covers the monitoring specifications in wesb.pbd, except for the naming differences in the metric nodes and paths.

There are two ways to handle this.

1. Just use wps.pbd and remove wesb.pbd from being included.

 

OR

 

2. Leave both enabled but modify the wesb.pbd as per below.

 

Edit wesb.pbd: comment out (disable) these lines:

  SetTracerClassMapping: BOMapBlamedFaultTracer com.wily.introscope.agent.trace.hc2.MethodThrewErrorReportingTracer com.wily.introscope.probebuilder.validate.MetricNameValidator

  SetTracerParameter: BOMapBlamedFaultTracer useblame false

  SetTracerClassMapping: MedPrimBlamedFaultTracer com.wily.introscope.agent.trace.hc2.MethodThrewErrorReportingTracer com.wily.introscope.probebuilder.validate.MetricNameValidator

  SetTracerParameter: MedPrimBlamedFaultTracer nameformatter com.wily.powerpack.websphereprocserver.nameformatter.MediationPrimitiveFormatter

  SetTracerParameter: MedPrimBlamedFaultTracer useblame false

 

Save the changes in the wesb.pbd and restart.

 

Environment

Release: CEMUGD00200-9.7-Introscope to CA Application-Performance Management-Upgrade Main
Component: