BMC Middleware and Transaction Management - MainView Monitoring Extension (qpmainview) throwing OutOfMemoryError exception

Version 1
    Share:|

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


    PRODUCT:

    TrueSight Middleware Monitor


    APPLIES TO:

    BMC Middleware Management - Transaction Monitoring



    PROBLEM:

     

    Symptoms:
      

    OutOfMemoryError exception in qpmainview.log. MainView Monitoring Extension not monitoring properly.

      

    Example Log Messages:

      

    No objects were monitored for the MainView server called SVR1
    java.lang.OutOfMemoryError: GC overhead limit exceeded
    MonitorState didn't complete
    java.lang.OutOfMemoryError: GC overhead limit exceeded

      
    Applies To:
      

    BMC Middleware and Transaction Management
    BMC Middleware Management - Performance and Availability
    BMC Middleware Management - Transaction Monitoring
     

     


    SOLUTION:

     

    Legacy ID:KA427748

      
    Cause:
      

    The JVM's heap space has been exhausted, most likely by the amount of monitored objects.

      
    Solution:
      

    Raise the JVM's maximum heap space.

      

    On Windows:

      
       
    • In the directory where the MainView Monitoring Extension is installed, locate the file called "qpmainview.conf" and open it in a text editor.
    •  
    • Find the lines similar to those below:

      # Initial Java Heap Size (in MB)
      wrapper.java.initmemory=12

      # Maximum Java Heap Size (in MB)
      # Increase this if you see OutOfMemoryErrors in the log.
      wrapper.java.maxmemory=1024
    •  
    • Increase the value for wrapper.java.maxmemory as required, for example double it.
      

    On UNIX:

      
       
    • In the directory where the MainView Monitoring Extension is installed, locate the file called "qpmainview.sh" and open it in a text editor.
    •  
    • Find the line that looks similar to this:

      Program="java -Dmqsext=qpmainview $gcpolicy -Xmx1024m -classpath $EXT_CLASSPATH com.mqsoftware.Extensions.qpmainview.qpmainview"
    •  
    • Change the value for the "-Xmx" parameter as required, for example double it.
      
    Additional Information:
      

    On Windows, the extension has been designed to run with a 32bit JRE. This imposes some limitations as to how big the value for "wrapper.java.maxmemory" can be set. If the extension requires more memory than it can get from a 32bit JRE, then get in touch with BMC Customer Support and request support for a 64bit JRE on Windows.
     

      

     

     


    Article Number:

    000087309


    Article Type:

    Solutions to a Product Problem



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