DX Application Performance Management

Expand all | Collapse all

Error in the JMS registered in the AutoProbe

Jump to Best Answer
  • 1.  Error in the JMS registered in the AutoProbe

    Posted 02-09-2018 04:26 PM

    We are implementing an OSB 12c, but the following error is recorded in the AutoProbe log file:

     

    Unable to instrument. Invalid settings provided: 3 Can not proceed because there are conflicting tracer class mappings for JMSBackendTracer.

     

    Do you know what you could owe?
    I attach the log files.



  • 2.  Re: Error in the JMS registered in the AutoProbe

    Posted 02-09-2018 06:37 PM

    Dear Carlos:

         If no one responds to this by your Monday morning, please consider opening a case. If you do so, it would be so helpful to others if you posted your progress and the found solution.

     

    Thanks 

    Hal German



  • 3.  Re: Error in the JMS registered in the AutoProbe
    Best Answer

    Posted 02-11-2018 04:42 PM

    Hi Carlos,

    It looks like you are using 10.3 and JMSBackendTracer is defined in both jms.pbd and Oracle-SOA-BPEL.pbd.

    For 10.3+ I found advice in an internal document setup for WebLogic 12c with OSB to:

    1. Comment out jms.pbd in weblogic-typical.pbl 

    2. Comment out these lines in toggles-typical.pbd:

    #######################
    # JMS Configuration
    # ================
    #TurnOn: JMSListenerTracing
    #TurnOn: JMSConsumerTracing

    #######################
    # EJB 2.0 Configuration
    # ================
    #TurnOn: EJB2StubTracing
    #TurnOn: SessionBeanTracing
    #TurnOn: EntityBeanTracing
    #TurnOn: MessageDrivenBeanTracing
    # TurnOn: EJBMethodLevelTracing

    #######################
    # EJB 3.0 Configuration
    # ================
    #TurnOn: EJB3StubTracing
    #TurnOn: SessionBean3Tracing
    #TurnOn: EntityBean3Tracing
    #TurnOn: MessageDrivenBean3Tracing
    #TurnOn: EJB3MethodLevelTracing

     

    Hope that helps

     

    Thanks

     

    Lynn