IBM Support

JR57182: LOGGING NUMEROUS ASSETS IS SLOW WHEN YOU USE THE TOSTRING() METHOD OF THE MANAGEDASSETCLASSLOADER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The public method toString() of the ManagedAssetClassLoader
    prints the internal details of its classloader and the details
    of all its managed assets.
    
    For example, the ScopeManager class prints information about any
    unknown or unexpected classloader it encounters at run time,
    resulting in log statements like
    
        [12/7/16 11:17:14:571 GMT-05:00] 0000015d ScopeManager
    CWLAG0209I: A foreign classloader  * * *
    com.lombardisoftware.server.core.ManagedAssetClassLoader * * *
    
    As a result, performance slows down when numerous assets are
    being logged.
    

Local fix

Problem summary

  • Any code that uses an instance of ManagedAssetClassloader in its
    logging invokes the public toString() method, potentially
    causing the time-consuming logging algorithm to run although the
    detailed information is not required.
    
    PRODUCTS AFFECTED
    IBM Business Process Manager (BPM) Advanced
    IBM BPM Standard
    IBM BPM Express
    

Problem conclusion

  • A fix is available for IBM BPM V8.5.7 cumulative fix 2017.03
    that changes the the public toString() method so that only the
    key data, such as the class name and the current and the initial
    size of the static ManagedAssetClassLoader cache, is printed.
    With this fix installed, additional details are logged by the
    specific class trace only.
    
    Furthermore, the ManagedAssetClassLoader class has been removed
    from the component logger WLE.wle=all. You can trace the
    ManagedAssetClassLoader class by using the trace specification
    
    "com.lombardisoftware.server.core.*=finer" -> logs the entry and
    exit trace events
    "com.lombardisoftware.server.core.*=finest" -> adds log for the
    ManagedAssetClassLoader details (formerly done by toString())
    
    To determine whether the cumulative fix is available, complete
    the following steps on Fix Central
    (http://www.ibm.com/support/fixcentral):
    
    1. On the Select product tab, select WebSphere as the product
    group, IBM Business Process Manager with your edition from the
    WebSphere options, All as the installed version, and All as the
    platform, and then click Continue.
    2. In the Text field, enter "cumulative fix", and click
    Continue.
    
    If cumulative fix 2017.03 is available, download and install it.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR57182

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    856

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-12-16

  • Closed date

    2017-02-01

  • Last modified date

    2017-02-01

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

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

Fix information

  • Fixed component name

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R856 PSY

       UP

  • R857 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"856","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
01 February 2017