IBM Support

PH32277: APPLICATION DEPLOYMENT IS SLOW WHEN APPLICATION HAS MANY EJB JARS

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

  • When the application contains many EJB JAR files, the
    application server might spend too much time searching for
    remote EJBs. This can delay the deployment of the application.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server that have applications which         *
    *                  contain many EJB JAR files.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Application deployment is slow for      *
    *                      applications which contain many EJB     *
    *                      JAR files.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    WebSphere Application Server searches for remote EJBs when
    deploying an application.  It does so by reading the class
    files in EJB JARs to find classes or super classes which
    implement java.rmi.Remote interface.  This delays the
    deployment of the application when many EJB JAR files are
    present, and is unnecessary when the application does not
    contain remote EJBs.
    

Problem conclusion

  • New MANIFEST.MF attributes are defined which allow you to
    specify a list of remote EJBs.  When these attributes are
    present, WebSphere Application Server will use the specified
    list.  This will avoid the search for remote EJBs.
    
    To enable the fix, add IBM-Enable-Remote-EJB-List = true to
    MANIFEST.MF of the EAR. é á é áIf the application does not conta
    remote EJBs, you are finished. é á é á é áHowever, if the applic
    contains remote EJBs, the attribute IBM-Remote-EJB-List must
    be used to specify the remote EJB names.  Separate the remote
    EJB names using ",".
     é á
    Example 1:
    
        Add the following attributes to META-INF/MANIFEST.MF of
    the application when there are 2 remote EJBs named remoteEJB1
    and remoteEJB2.
    
    IBM-Enable-Remote-EJB-List = true
    IBM-Remote-EJB-List = remoteEJB1, remoteEJB2
    
    Example 2:
    
        Add only the following to attribute to META-INF/
    MANIFEST.MF of the application when the application does NOT
    contain remote EJBs.
    
    IBM-Enable-Remote-EJB-List = true
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.20 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

    PH32277

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-12-03

  • Closed date

    2020-12-09

  • Last modified date

    2020-12-09

  • 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":"900"}]

Document Information

Modified date:
10 December 2020