IBM Support

PH20328: WSADMIN RENAMENODE() AND ADMINCONFIG.SAVE() COMMANDS DELETING WSBUNDLEMETADATA/JSF-MYFACES.XML

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

  • I tried the renameNode() and AdminConfig.save() in the connected
    mode in AppSrv03. And turned on the following traces:
    com.ibm.ws.management.*=all:com.ibm.wsspi.management.bla.framewo
    rk.*=all
    
    and found that when AdminConfig.save() is in progress, the
    folders under
    C:\85515_cf151904.01\WebSphere\AppServer\profiles\AppSrv03\serve
    rs\server1\configuration were getting deleted and the
    corresponding trace snippet responsible for this was as below
    
        [12/5/19 13:43:27:579 CST] 0000009e BLABinaryProc 3
    postProcess
                                        Invoking repositoryOpDone.
    syncHandler=com.ibm.ws.runtime.selectableBundles.SelectableBundl
    eSyncHandler@e5428a15
        [12/5/19 13:43:27:579 CST] 00000096 FileUtils    > delete
    Entry
    
    file=C:\85515_cf151904.01\WebSphere\AppServer\profiles\AppSrv03\
    servers\server1
        [12/5/19 13:43:27:579 CST] 00000096 FileUtils    > _delete
    Entry
    
    file=C:\85515_cf151904.01\WebSphere\AppServer\profiles\AppSrv03\
    servers\server1
                                        followLink=true
    
    
    The BLABinaryProcess calls the runtime code
    selectableBundleSynchandler which is deleting the
    folders for some reason.
    
    Looks like selectableBundleSynchandler code is owned by the
    runtime. Please pass on to the runtime team to investigate
    further.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  the renameNode command and the renameNode   *
    *                  AdminTask command.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Applications may fail or exhibit        *
    *                      unexpected behavior after renaming      *
    *                      the node which contains the hosting     *
    *                      Application Server.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During execution the renameNode command unexpectedly removes
    the wsBundleMetadata directory within the profile of each
    applcation server contained by the node. Files in the
    wsBundleMetaData directory effect the versions of Java
    Enterprise Edition feature API and runtime an application
    server will support -- such as Java Server Faces version 1.2
    or 2.0. When these files are missing, the application server
    will support the default version of any selectable feature
    API and runtime, which may differ from that configured for an
    application deployed on the server. This difference can cause
    applications to fail or exhibit unexpected behaviors anytime
    during the application lifecycle.
    The renameNode command invokes the administrative command
    "renameNode" of the AdminTask object, and then synchronizes
    the configuration changes. For example:
    AdminTask.renameNode( óÔé¼ £[-nodeName <node01> -newNodeName
    <dmgrnode01>] óÔé¼Ôäó)
    AdminConfig.save()
    The problem will also occur when executing these commands using
    the wsadmin administrative utility.
    

Problem conclusion

  • Apply APAR PH20328 to prevent the renameNode command from
    removing the wsBundleMetaData profile directory for servers
    contained by the renamed node.
    
    The fix for this APAR is targeted for inclusion in fix packs
    8.5.5.18 and 9.0.5.3. For more information, see 'Recommended
    Updates for
    WebSphere Application Server':
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH20328

  • 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-12-16

  • Closed date

    2020-01-23

  • Last modified date

    2020-01-23

  • 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 #: PH20328

Modified date: 23 January 2020