IBM Support

PM68498: APPLICATIONS DEPLOYED WITHOUT A CUSTOM CLASSLOADER ELEMENT ARE I NCORRECTLY ABLE TO ACCESS CLASSES FROM THE LIBERTY PROFILE RUNTI

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Applications without a custom classloader have unexpected
    dependencies due to being able to incorrectly resolve and use
    packages outside of the default visibility, ibm-api and spec.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile without a            *
    *                  classloader element specified for the       *
    *                  application.                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Applications deployed without a         *
    *                      custom classloader are incorrectly      *
    *                      able to access packages from the        *
    *                      Liberty profile runtime.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Applications running without a custom classloader
    configuration (the default) will find themselves able to
    resolve and use packages outside of the default visibility
    (ibm-api & spec). This is not normal, and could result in an
    application being developed with unexpected dependencies.
    The most commonly seen scenario is the resolution to the SLF4J
    packages shipped with the Liberty Profile rather than those
    users place within their application.
    

Problem conclusion

  • The error preventing the application of restrictions in the
    default case was remedied, by ensuring that the information
    required for them to become active is always added, rather
    than being added conditionally, where some sub cases omitted
    the enabling of the restrictions in error.
    
    
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.0.1. Please refer to the Recommended Updates page
    for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM68498

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-07-10

  • Closed date

    2012-09-26

  • Last modified date

    2012-10-04

  • 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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021