App Visibility - Receiving "Blocking insertion due to high memory consumption was ended" messages in the App Visibility Collector log file called collector.log

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    TrueSight App Visibility Manager Server


    COMPONENT:

    App Visibility Collector


    APPLIES TO:

    App Visibility Collector - All Versions



    PROBLEM:

    The App Visibility Collector log file called collector.log contains a number of the "Blocking insertion due to high memory consumption was ended" error messages, which causes all applications to not receive any App Visibility and Synthetic data.


    CAUSE:

    Memory consumption in the App Visibility Collector consumption in App Visibility Collector exceeded the defined threshold.


    SOLUTION:

    First, ensure the server with the App Visibility Collector has plenty of free system memory.

    Second, if there are plenty of free system memory then the maximum memory defined for the App Visibility Collector is low.  For example, if the App Visibility Collector's maximum memory is 2Gb, and it is using more than 85% of the 2Gb at the time then the "Blocking insertion due to high memory consumption" error messages will be generated.

    A memory consumption message for the App Visibility Collector will be generated in the Health Events (health-events.csv) within the App Visibility Portal console.  Below is a sample of that message:

    Memory consumption in the App Visibility Collector xyz2237.abc123.int:8200,Memory consumption in App Visibility Collector 'https://xyz2237.abc123.int:8200' has exceeded the defined threshold and is at 91.315%,

    To resolve this issue, increase the App Visibility Collector service memory to 4Gb by performing the following steps:

    Linux Server:
    1) Stop the App Visibility Collector process

    2) Open /etc/bmc/collectorDaemon.conf and update the following lines and then save the conf file:
    INITIAL_MEMORY=4096
    MAXIMUM_MEMORY=4096

    3) Restart the App Visibility Collector process

    Windows Server:
    See the "To change the heap size of App Visibility components on Windows" section in the following link:
    https://docs.bmc.com/docs/applicationmanagement/113/changing-the-heap-size-on-app-visibility-components-772581806.html

    Another solution would be to add the larger memory values to the system registry.  To do this, follow the below steps on the same system where the App Visibility Collector is installed:
    a) Stop the App Visibility Collector service.
    b) Change the value in the registry under this key to reflect the higher memory values:
    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Apache Software Foundation\Procrun 2.0\adop_collector\Parameters\Java
    c) Restart the App Visibility Collector machine. (These higher values will not be used until the system is restarted.)


    Article Number:

    000113590


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles