IBM Support

PK48447: CLUSTER CREATION IN A CELL WITH A LARGE NUMBER OF SERVERS IS EXTREMELY SLOW AND CAN CAUSE 100% CPU CONDITION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Cluster creation in a cell with a large number of servers is
    extremely slow, and can cause a 100% CPU condition. Also, a
    large portion of the memory will be used up by workspace
    objects:
    
    
    at
    com.ibm.ws.sm.workspace.impl.WorkSpaceManagerImpl.createWorkSpac
    e(WorkSpaceManagerImpl.java(Compiled Code))
    at
    com.ibm.ws.sm.workspace.impl.WorkSpaceManagerImpl.getWorkSpace(W
    orkSpaceManagerImpl.java(Compiled Code))
    at
    com.ibm.ws.sm.workspace.impl.WorkSpaceManagerImpl.getWorkSpace(W
    orkSpaceManagerImpl.java(Compiled Code))
    at
    com.ibm.ws.sm.workspace.impl.WorkSpaceManagerImpl.getWorkSpace(W
    orkSpaceManagerImpl.java(Inlined Compiled Code))
    at
    com.ibm.ws.management.configservice.WorkspaceHelper.getWorkspace
    (WorkspaceHelper.java(Compiled Code))
    at
    com.ibm.ws.management.configservice.WorkspaceHelper.getScopeCont
    exts(WorkspaceHelper.java(Compiled Code))
    at
    com.ibm.ws.management.configservice.RootObjectDelegator.getAll(R
    ootObjectDelegator.java(Compiled Code))
    at
    com.ibm.ws.management.configservice.ConfigServiceImpl.queryConfi
    gObjects(ConfigServiceImpl.java(Compiled Code))
    at
    com.ibm.ws.management.configservice.ConfigServiceServerProxy$10.
    run(ConfigServiceServerProxy.java(Compiled Code))
    at java.security.AccessController.doPrivileged1(Native Method)
    at
    java.security.AccessController.doPrivileged(AccessController.jav
    a(Compiled Code))
    at
    com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon
    troller.java(Compiled Code))
    at
    com.ibm.ws.management.configservice.ConfigServiceServerProxy.que
    ryConfigObjects(ConfigServiceServerProxy.java(Compiled Code))
    at
    com.ibm.ws.management.wlm.ClusterMgr.loadClusterConfig(ClusterMg
    r.java:441)
    at
    com.ibm.ws.management.wlm.ClusterMgr.loadRefreshClusters(Cluster
    Mgr.java:662)
    at
    com.ibm.ws.management.wlm.ClusterMgrNotificationHandler.configCh
    anged(ClusterMgr.java:1485)
    at
    com.ibm.ws.management.wlm.ClusterMgrNotificationHandler.access$3
    00(ClusterMgr.java:1366)
    at
    com.ibm.ws.management.wlm.ClusterMgrNotificationHandler$1.run(Cl
    usterMgr.java:1424)
    at
    com.ibm.ws.security.auth.distContextManagerImpl.runAs(distContex
    tManagerImpl.java(Compiled Code))
    at
    com.ibm.ws.security.auth.distContextManagerImpl.runAsSystem(dist
    ContextManagerImpl.java:2667)
    at
    com.ibm.ws.management.wlm.ClusterMgrNotificationHandler.run(Clus
    terMgr.java:1431)
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IBM Websphere Application Server versions    *
    *                 6.0.2 and 6.1 users who try to create        *
    *                 a cluster.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Cluster creation in a cell with a       *
    *                      large number of servers is extremely    *
    *                      slow, and can cause a 100% CPU          *
    *                      condition. Also, a large portion of     *
    *                      the memory will be used up by           *
    *                      workspace objects.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    As the API queryConfigObjects tries to load all resources in
    the configuration into the workspace as part of cluster
    creation and it takes high CPU usage.
    

Problem conclusion

  • Code has been changed to use a different API which only loads
    the specific file specified in the scope instead of the
    queryCOnfigObject.
    
    The fix for this APAR is currently targeted for inclusion
    in fix packs 6.0.2.25 and 6.1.0.15.
    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

    PK48447

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    60A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-07-06

  • Closed date

    2007-10-25

  • Last modified date

    2007-10-25

  • 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

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021