IBM Support

IJ33726: MEMORY LEAK WITH LOG4J OUTPUTSTREAMMANAGER HASHMAP ENTRIES

Direct links to fixes

7.1.0-TIV-NCI-FP0023-README
7.1.0-TIV-NCI-SOLARIS-FP0023
7.1.0-TIV-NCI-AIX-FP0023
7.1.0-TIV-NCI-WINDOWS-FP0023
7.1.0-TIV-NCI-ZLINUX-FP0023
7.1.0-TIV-NCI-LINUX-FP0023
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 23 (7.1.0-TIV-NCI-FP0023)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This APAR is supplementary to IJ31120 to clean up log4j
OutputStreamManager HashMap entries.

Local fix

  • 



Problem summary


    

  • ****************************************************************
* USERS AFFECTED:                                              *
* All Impact Users                                             *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* A memory leak was discovered in the logging handler for the  *
* Impact server. The log4j2 log manager was mis-configured and *
* creating multiple OutputStreamManager each time a log was    *
* initialized.                                                 *
****************************************************************
* RECOMMENDATION:                                              *
* NONE                                                         *
****************************************************************
The memory leak can be observed by adding "-Dlog4j2.debug" to
<IMPACT_HOME>/wlp/usr/servers/NCI/jvm.options

When the log manager starts a log, it will spawn additional
instances of an OutputStreamManager each time.

DEBUG StatusLogger Starting OutputStreamManager
SYSTEM_OUT.false.false-87
DEBUG StatusLogger Starting OutputStreamManager
SYSTEM_OUT.false.false-88
TRACE StatusLogger New file
'/opt/IBM/tivoli/impact/logs/NCI_eventprocessor.log' created =
false

These instances are never removed from memory and can result in
an out of memory condition.

    



Problem conclusion


    

  • The log4j2 log manager configuration was corrected to avoid the
creation of extra OutputStreamManager instances.

The fix for this APAR is contained in the :
| Fix Pack | 7.1.0-TIV-NCI-FP0023

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IJ33726
    • 

  • Reported component name
    NETCOOL/IMPACT
    • 

  • Reported component ID
    5724O59IS
    • 

  • Reported release
    710
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2021-07-13
    • 

  • Closed date
    2021-07-26
    • 

  • Last modified date
    2021-07-26
    • 





    

  • APAR is sysrouted FROM one or more of the following:
    

    • 

  • APAR is sysrouted TO one or more of the following:
    

    • 



Modules/Macros


    

  • UNKNOWN

    



Fix information


    

  • Fixed component name
    NETCOOL/IMPACT
    • 

  • Fixed component ID
    5724O59IS
    • 



Applicable component levels


    

  • R710  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSSHYH","label":"Tivoli Netcool\/Impact"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                                                                    

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            05 November 2021
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback