IBM Support

PH37493: OSGI.CONFIGURATION.AREA.READONLY=TRUE NOT TAKING AFFECT FOR SERVANT REGION

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

  • -Dosgi.configuration.area.readOnly=true doesn't take affect in
    the servant region because there is logic in the OSGI to check
    if the server has crashed.  This logic doesn't work correctly in
    a control/servant/adjunct environment.  So the check will be
    disabled on z/OS.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  V8.5.5 and V9.0                             *
    ****************************************************************
    * PROBLEM DESCRIPTION: Setting -                               *
    *                      Dosgi.configuration.area.readOnly=true  *
    *                      is                                      *
    *                      ineffective                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The WAS bootstrap logic includes an attempt at detecting whether
    the server has crashed without a proper shutdown in its previous
    instance, in which case the OSGi framework is started in "clean"
    mode (discarding and rebuilding the contents of the OSGi
    configuration area). When that clean start is performed, some
    configuration options, particularly the option to process the
    configuration in read-only mode, are unavailable.
    On z/OS, it was determined that the crash detection logic was
    faulty, detecting a "crash" on every server start and attempting
    a clean OSGi framework start. Because of this, the read-only
    property could never effectively be enabled.
    

Problem conclusion

  • The crash detection logic and automatic OSGi clean was disabled
    z/OS. Customers experiencing crashes should manually run the
    osgiCfgInit.sh script before their next server startup.
    
    The fix for this APAR is targeted for inclusion in fix packs
    8.5.5.21 and 9.0.5.11. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH37493

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-05-24

  • Closed date

    2021-11-03

  • Last modified date

    2021-11-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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

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

Document Information

Modified date:
04 November 2021