IBM Support

PH30511: FAILED TO CREATE DYNAMIC CLUSTER AND SEEING LOTS OF WKSP0501I: XX WORKSPACES EXIST IN THE WSTEMP DIRECTORY.

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

  • In the WebSphere Network Deployment environment, there is
    possibility that dynamic cluster creation fails after creating
    multiple workspaces.
    
    Dmgr logs showed a log of
    WKSP0501I: xx workspaces exist in the wstemp directory.
    
    Workspace stack showed a looping indefinitely to a call of
    AdminDatImpl.initialization which cause workspace keep getting
    created and never get clean up.
    Call stack info of
    createWorkSpace(prop), workspace id anonymous1601467961800: com.
    ibm.ws.sm.workspace.impl.WorkSpaceManagerImpl.getCallStack(WorkS
    paceManagerImpl.java:636)
    ...
    com.ibm.ws.management.configservic
    e.ConfigServiceServerProxy.resolve(ConfigServiceServerProxy.java
    :558)
    com.ibm.ws.management.commands.nodegroup.NodeGroupHelper.g
    etNodeGroupMembers(NodeGroupHelper.java:89)
    
    sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source)
    sun
    .reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcc
    essorImpl.java:55)
    java.lang.reflect.Method.invoke(Method.java:
    508)
    com.ibm.ws.security.config.AdminDataImpl.getNodeGroupMember
    s(AdminDataImpl.java:853)
    com.ibm.ws.security.config.AdminDataIm
    pl.getCurrentNodeGroupNames(AdminDataImpl.java:802)
    com.ibm.ws.s
    ecurity.config.AdminDataImpl.initialization(AdminDataImpl.java:2
    70)
    com.ibm.ws.security.config.AdminDataImpl.<init>(AdminDataIm
    pl.java:108)
    com.ibm.ws.security.config.SecurityConfigObjectFact
    oryImpl.createAdminData(SecurityConfigObjectFactoryImpl.java:137
    )
    ....
    com.ibm.ws.management.configservice.ConfigServiceServerPr
    oxy.resolve(ConfigServiceServerProxy.java:558)
    com.ibm.ws.manage
    ment.commands.nodegroup.NodeGroupHelper.getNodeGroupMembers(Node
    GroupHelper.java:89)
    
    sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source)
    sun
    .reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcc
    essorImpl.java:55)
    java.lang.reflect.Method.invoke(Method.java:
    508)
    com.ibm.ws.security.config.AdminDataImpl.getNodeGroupMember
    s(AdminDataImpl.java:853)
    com.ibm.ws.security.config.AdminDataIm
    pl.getCurrentNodeGroupNames(AdminDataImpl.java:802)
    com.ibm.ws.s
    ecurity.config.AdminDataImpl.initialization(AdminDataImpl.java:2
    70)
    com.ibm.ws.security.config.AdminDataImpl.<init>(AdminDataIm
    pl.java:108)
    com.ibm.ws.security.config.SecurityConfigObjectFact
    oryImpl.createAdminData(SecurityConfigObjectFactoryImpl.java:137
    )
    ..... com.ibm.ws.management.configservice.ConfigServiceServerP
    roxy.resolve(ConfigServiceServerProxy.java:558)
    com.ibm.ws.manag
    ement.commands.nodegroup.NodeGroupHelper.getNodeGroupMembers(Nod
    eGroupHelper.java:89)
    
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.
    reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl
    .java:90)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(Delega
    tingMethodAccessorImpl.java:55)
    java.lang.reflect.Method.invoke
    (Method.java:508)
    com.ibm.ws.security.config.AdminDataImpl.getNo
    deGroupMembers(AdminDataImpl.java:853) com.ibm.ws.security.confi
    g.AdminDataImpl.getCurrentNodeGroupNames(AdminDataImpl.java:802)
    
    com.ibm.ws.security.config.AdminDataImpl.initialization(AdminD
    ataImpl.java:270)
    com.ibm.ws.security.config.AdminDataImpl.<ini
    t>(AdminDataImpl.java:108)
    ... keep repeating indefinitely.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  Network Deployment                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: The dynamic cluster creation fails with *
    *                      multiple workspaces left behind.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During the dynamic cluster creation, there is a possibility that
    WebSphere creates wstemp workspace unnecessarily multiple times
    and fails to create the cluster.
    

Problem conclusion

  • The bug has been fixed.
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.19 and 9.0.5.7. 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

    PH30511

  • 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

    2020-10-13

  • Closed date

    2020-10-28

  • Last modified date

    2020-10-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

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

Document Information

Modified date:
29 October 2020