IBM Support

PH19420: PLUGIN PROPAGATION FOR MANAGED DEFINITION ON REMOTE NODE FAILS TO COPY PLUGIN-KEY.KDB TO WEBSERVER LOCATION ON THE REMOTE NODE

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

  • Propagation of plugin-key.kdb (Copy button in console under
    webserver>Plug-in Properties) fails for a managed webserver
    definition where the WAS Node and webserver are remote from
    DMGR. While the file appears to have been copied from DMGR to
    the remote Node the copy from remote node config repository to
    the webserver location defined in plugin-cfg.xml does not
    complete.
    Tracing suggested the Node Sync process used to copy
    the file to the remote node was not complete before the Plugin
    auto prop code at the remote node started to try and do the
    local copy at the remote node from remote node config
    repository to the webserver location defined in plugin-cfg.xml.
    

Local fix

  • Manual copy of plugin-key.kdb
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Remote node plugin-key.kdb isn't        *
    *                      propagated to webserver location.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Occasionally it is seen that when the plugin is attempting to
    copy the plugin-key.kdb from the remote node's repository
    location, an error is produced indicating it isn't able to
    read the server.xml file.  In those cases, the node sync
    associated with the server.xml update had not completed at the
    time propagation was in process.
    

Problem conclusion

  • The plugin code has be modified to have a node sync monitor
    which ensures that the node sync is complete before attempting
    the propagation processing.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.17 & 9.0.5.3.  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

    PH19420

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-11-19

  • Closed date

    2019-12-11

  • Last modified date

    2019-12-11

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PH19420

Modified date: 11 December 2019