IBM Support

PM18624: RETRIEVE ALL CHILDREN OF PARENT CONTEXT ONLY WHEN CONTEXTTYPE IS NULL IN ROOTOBJECTDELEGATOR.GETCHILDREN() METHOD

Fixes are available

7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • In RootObjectDelegator.getChildren(..), all the children of
    the parent context are retrieved (instantiated as
    RepositoryContextImpls) and then filtered according to
    document type. The problem with this method is that if the
    workspace is saved (synch'ed), then directories and files are
    created for each RepositoryContextImpl instance in the temporary
    workspace. This is an unnecessary burden. Since there is a way
    to ask a RepositoryContextImpl for its children of a specific
    context type (which does not instantiate contexts for ALL
    children), we should use that method if possible.
    
    Change RootObjectDelegator.getChildren() to take a specific
    context type and only instantiates children that  match that
    type.
    
    Using this small change, an improvement of 11 sec,
    12.5%, in response time for one of our key scenarios (Direct
    Deploy from Modeler to WPS). In this case, this change
    prevents a lot of files and directories from being created in
    the temporary workspace such as .../<cell>/applications/*,
    .../<cell>/blas/*, .../<cell>/cus/*, which are normally
    created when trying to find anything at the cell level (for
    example, resolving a specific node,
    configService.resolve(session, "Cell=qcell:Node=qnode"); ).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: In RootObjectDelegator                  *
    *                      getChildren() method, all the           *
    *                      children of the parent are retrieved    *
    *                      and then filtered according to          *
    *                      document type.  The problem with this   *
    *                      method is that if the workspace is      *
    *                      saved then directoriess and files are   *
    *                      created for each                        *
    *                      RepositoryContextImpl instance in the   *
    *                      temporary workspace. This is an         *
    *                      unnecessary burden. Since there is a    *
    *                      way to ask a RepositoryContextImpl      *
    *                      for its children of a specific          *
    *                      context type which does not             *
    *                      instantiate contexts for ALL            *
    *                      children, it can improve the            *
    *                      performance to deploy applications.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The existing RootObjectDelegator.getChildren() method
    has retrieved all children of the parent document type
    and filtered the context according to the document
    type. This has resulted in fetching more subdirectories and
    files than necessary.  It is more efficient to just retrieve
    the contexts of children with the correct type. Use of the
    RepositoryContext.getChildren method takes a
    RepositoryContextType and only instantiates children that
    match that type.
    

Problem conclusion

  • The APAR has changed the existing
    RootObjectDelegator.getChildren() method to only retrieve the
    contexts of children with the correct type as stated in the
    problem summary.  The change will improve a lot of application
    deployment performance.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.13.  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

    PM18624

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-07-16

  • Closed date

    2010-08-04

  • Last modified date

    2010-08-04

  • 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

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM18624

Modified date: 04 August 2010