IBM Support

PI51184: CWWKG0031E is received after commenting out a JNDI element and t hen adding it back at runtime

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If you define a JNDI element in the server.xml file,
    
    <jndiEntry value="xxxx"
    jndiName='jndi/xxxx'>
    
    Then you start the Liberty server, comment this entry out
    and
    save the change. After that, when you uncomment this entry,
    you'll find the following exception in the log:
    
    [10/19/15 8:39:10:222 CEST] 0000005a
    com.ibm.ws.config.xml.internal.ConfigUpdater
    E
    CWWKG0031E: The value jndi/xxxx specified for unique
    attribute
    jndiName is already in use.
    

Local fix

  • Assigning a unique id for the element
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
    *                  Liberty Profile who have two JNDI entry     *
    *                  elements in their server.xml file and       *
    *                  change the values or names while the server *
    *                  is running.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: When you have two JNDI elements         *
    *                      enabled, if you remove and then re-add  *
    *                      one you see an error message            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If you have two JNDI entry elements and you comment out one of
    them and then comment it back in, or change the values of the
    elements around and then switch them back you see an error
    message and the JNDI entries are not properly updated. This only
    occurs under certain circumstances and is related to the order
    in which Liberty profile updates the server configuration.
    

Problem conclusion

  • This problem has been fixed by adding an extra check if an
    update fails to see if a later update will allow the current
    update to be implemented.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.9.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • The workaround is to assign ID's to the JNDI entries.
    

Comments

APAR Information

  • APAR number

    PI51184

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-10-26

  • Closed date

    2016-01-08

  • Last modified date

    2016-01-08

  • 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

  • R855 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
14 October 2021