IBM Support

PH61169: AFTER PH56263, WEBSERVER FAILS TO START WHEN NOT DEFINING KDB AND STH

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

  • After PH56263, the customer could experience issues with the
    webserver startup when there is an https transport in the
    plugin-cfg.xml but plugin-key.kdb and
    plugin-key.sth does not exist, despite specifying
    useInsecure="true".
    
    Example message:
    [16/Apr/2024:10:32:56.03520] 000a0985 a4161500 - ERROR: lib_sxp:
    sxpParse: (Invalid characters or malformed sections within
    Plugin's XML file) End element returned FALSE for Transport.
    

Local fix

  • Remove all https transport in the plugin-cfg.xml
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of Plugins for WebServers who         *
    *                  define secure transports without defining   *
    *                  key database and stash files.               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Startup failure when a secure           *
    *                      transport is defined without kdb and    *
    *                      sth files, despite enabling the         *
    *                      useInsecure parameter.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Startup failure when a secure
    transport is defined without kdb and
    sth files, despite enabling the
    useInsecure parameter.
    

Problem conclusion

  • The code was updated to allow startup to proceed in this case.
    At runtime, useInsecure will use HTTP transports.
    
    The fix for this APAR is targeted for inclusion in fix packs
    8.5.5.26 and 9.0.5.21.
    For more information, see 'Recommended Updates for WebSphere
    Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

  • Create and define kdb and sth files for the secure transport.
    

Comments

  • 
    

APAR Information

  • APAR number

    PH61169

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-04-30

  • Closed date

    2024-05-24

  • Last modified date

    2024-05-28

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
21 August 2024