IBM Support

IT21381: JARS IN SHARED-CLASSES FOLDER NOT LOADED IF THE SAME CLASSES AREPRESENT IN LOCAL MQ JARS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When attempting to use jars through the shared-classes
    directory, if they contain classes that are defined in the MQ
    local jars, the shared-classes jars will be ignored, and the
    MQ local version will be loaded. For example, bouncycastle jars
    are included in the MQ local jars, resulting in any
    bouncycastle jars included in shared-classes being ignored.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v10.0.0.8 or above adding jars
    to the classpath using the shared-classes folder.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When adding a jar to the shared-classes directory for use in the
    Java compute node, if the classes also exist in the MQ prereq
    jars shipped with the product then the classes will be loaded
    from the MQ prereq jars, rather than the user jars. For example,
    bouncy castle jars are shipped as part of the local copy of MQ,
    so any bouncy castle jars in the shared-classes directory would
    be ignored.
    
    This may cause customer java code to behave in unexpected ways.
    

Problem conclusion

  • Classloading has been changed for MQ jars, removing the possible
    conflicts from the classpath of the java compute nodes.
    
    A new environment variable has been defined:
    MQSI_DISABLE_SHIPPED_MQ
    If this has been set, the shipped MQ jars will be removed from
    the class path, and the use of MQ dependant nodes in the product
    will be disabled.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.10
    v9.0       9.0.0.9
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT21381

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-07-11

  • Closed date

    2017-09-27

  • Last modified date

    2017-09-27

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

  • RA00 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 September 2017