IBM Support

PM86337: AUTHCACHE SIZES DO NOT SPECIFY A VALID RANGE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The maxSize and minSize properties of the authCache element
    are specified as type Integer, but do not specify any range.
    The correct range should be:
    0 < initialSize <= maxSize <= MAX INT (2^31-1 if they have
    that much memory.)
    
    If initialSize > maxSize, then show a warning message and
    internally set equal to maxSize to be forgiving and resilient
    in the development environment.
    
    
    Impact:
    The result of specifying invalid values for the above
    properties are:
    -ffdc's
    -error messages in the log
    -the authentication cache effectively being disabled
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Specifying an initial size for          *
    *                      an authentication cache element         *
    *                      outside of the allowable range causes   *
    *                      errors.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The modified() method in the AuthCacheServiceImpl class does
    not check the initial size specified for the authentication
    cache element against the maximum size specified. Initial
    sizes might be specified that are larger than the maximum,
    resulting in FFDCs and error messages in the log.
    

Problem conclusion

  • A minimum value was set in the authentication cache metatype
    for both the initialSize and maxSize attributes. The upper
    bound is now enforced in the AuthCacheServiceImpl by setting
    the initial size back to the maximum size when the initial
    size is specified to be larger than the maximum.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.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

    PM86337

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-04

  • Closed date

    2013-06-03

  • Last modified date

    2013-06-03

  • 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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 June 2013