Baseline_engine.QOS_MESSAGE queue is piling up and is yellow in the hub queue.

Document ID:  TEC1000777
Last Modified Date:  07/10/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Unified Infrastructure Management

Releases

  • CA Unified Infrastructure Management:Release:8.4
  • CA Unified Infrastructure Management:Release:8.41
  • CA Unified Infrastructure Management:Release:8.42

Components

  • UIM - BASELINE_ENGINE:UIMBAE
Symptoms:
  • The baseline_engine.QOS_MESSAGE queue has a large number of unprocessed items and appears to have stopped processing.
  • Memory for the baseline_engine probe will show to be at 100% of Xmx.
  • Processor usage may show to be equal to 1 core's worth of CPU availability.
  • Restarting the probe may allow it to process messages for a few minutes before coming to a halt again.
Environment:
baseline_engine 2.70 or greater
Cause:

This probe uses the log4j system for probe logging. There is a known issue with this SDK where it was discovered that if the thread that handles logging is unable to keep up with the amount of information being logged, it blocks other threads that do the real work of the probe.

Workaround:
  1. Navigate to the nimsoft\probes\SLM\baseline_engine directory
  2. Edit the log4j2.xml file
  3. Modify the AppenderRef lines to have ref="console" as shown below

    <Loggers>

        <Root level="info" additivity="false">

            <AppenderRef ref="console"/>

        </Root>

        <Logger name="PERFORMANCE" level="off" additivity="false">

            <AppenderRef ref="console"/>

        </Logger>

        <Logger name="MESSAGELIMIT" level="off" additivity="false">

            <AppenderRef ref="console"/>

        </Logger>

        <Logger name="com.ca.analytics.dmc.receive" level="info" additivity="false">

            <AppenderRef ref="console"/>

        </Logger>

        <Logger name="org.quartz" level="warn" additivity="false">

            <AppenderRef ref="console"/>

        </Logger>

        <Logger name="always" level="trace" additivity="false">

            <AppenderRef ref="console"/>

        </Logger>

        <Logger name="org.springframework" level="warn" additivity="false">

            <AppenderRef ref="console"/>

        </Logger>

        <Logger name="com.nimsoft.threshold.cmd" level="error" additivity="false">

            <AppenderRef ref="console"/>

        </Logger>

        <Logger name="com.nimsoft.derivedmetrics.performancestats" level="warn" additivity="false">

            <AppenderRef ref="console"/>

        </Logger>

        <Logger name="com.nimsoft.derivedmetrics.scriptlink" level="warn" additivity="false">

            <AppenderRef ref="console"/>

        </Logger>

    </Loggers>

 

-------------------------------------------------------------------------------------------------------

Attached is a uim probe package to update this file. Download and import into your archive, then deploy to the baseline servers. This probe package is not supported and given free to use to speed up deploying. Please test in your test system before deploying to production. It will also set baseline_engine loglevel = 0. 

 

 log4j2_1.2.zip

Additional Information:

This problem can affect other java based probes that use the log4j SDK for logging (such as the discovery_server probe and prediction_engine).

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >

Chat with CA

Just give us some brief information and we'll connect you to the right CA ExpertCA sales representative.

Our hours of availability are 8AM - 5PM CST.

All Fields Required

connecting

We're matching your request.

Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here.

  • {{message.agentProfile.name}} will be helping you today.

    View Profile


  • Transfered to {{message.agentProfile.name}}

    {{message.agentProfile.name}} joined the conversation

    {{message.agentProfile.name}} left the conversation

  • Your chat with {{$storage.chatSession.messages[$index - 1].agentProfile.name}} has ended.
    Thank you for your interest in CA.


    Rate Your Chat Experience.

    {{chat.statusMsg}}

agent is typing