IBM Support

PM18253: PREVENT ANNOTATION PROCESSING FOR WEB CONTEXT ROOT CHECKS AGAINST APPLICATION'S WITH NO DEPLOYMENT DESCRIPTOR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A fast path should be added to check the context root of
    existing installed applications with no application.xml
    deployment descriptor when installing a new application.  This
    is because costly annotation scanning will occur to determine
    the context root if no application deployment descriptor
    exists.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Installation of an enterprise           *
    *                      application takes a long time to        *
    *                      complete.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During enterprise application deployment, the check for a
    duplicate context root across all existing applications that
    are targeted to the same node as the new application causes a
    performance issue when there are existing enterprise
    applications with no application deployment descriptors in
    them.
    

Problem conclusion

  • A new custom property,
    com.ibm.websphere.management.application.persistWebContext, is
    provided to persist the web module context information in a
    deployment file. To set the custom property, follow one of the
    steps below:
    
    To enable the system property in the Administrative Console:
    a) In an Network Deployment environment, the system property
    needs to be set on the deployment manager.
    System administration --> Deployment manager --> Java and
    Process Management --> Process definition --> Java Virtual
    Machine --> Custom properties --> New
    Name :
    com.ibm.websphere.management.application.persistWebContext
    Value : true/false
    
    b) In a Base edition Application Server environment, the system
    property is set on server1.
    Servers --> Server Types --> WebSphere application servers -->
    server1 --> Java and Process Management --> Process definition
    --> Java Virtual Machine --> Custom properties --> New
    Name :
    com.ibm.websphere.management.application.persistWebContext
    Value : true/false
    
    To enable the system property when running wsadmin in local
    mode, it can be set as an option when starting wsadmin or in
    the wsadmin.properties file.
    a) To set the system property when starting wsadmin do the
    following:
    wsadmin -conntype NONE -javaoption
    "-Dcom.ibm.websphere.management.application.persistWebContext
    =<value>"
    where <value> can be true or false.
    
    b) To set the system property in the wsadmin.properties file
    found at <was_install>/profiles/<profile_name>/properties, add
    the following line with <value> being true or false:
    com.ibm.websphere.management.application.client.persistWebContex
    t=<value>
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.17.  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

    PM18253

  • 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-13

  • Closed date

    2011-01-27

  • Last modified date

    2012-06-13

  • 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

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

Document Information

Modified date:
24 October 2021