IBM Support

PM11652: USING EJB TAG, AFTER DEPLOYMENT, EJB-JAR.XML IS MISSING SOME OF THE REFERENCES.

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

  • developed Enterprise Java Bean (EJB) project using @EJB tag.
    After deployment of an EAR in WebSphere Application Server,
    the module's generated ejb-jar.xml has some of the
    references missing. It seems to be a problem when the
    ejb-jar.xml is generated in WebSphere Application Server v7.
    
    We have developed a Project interchange file to demonstrate this
    problem. There are 3 session ejb, each in one project.
    
    EJB_1 reference EJB_2 & EJB_2 reference EJB_3. When deploying
    the
    application we can only see ref from EJB_1 to EJB_2. This
    happens every time there is a chain of reference.
    
    We are using RAD 7.5.5 and WAS 7.0.0.7.
    To recreate the issue please follow the below steps.
    
    1. Deploy validation.jar in WAS 7.0.0.7.
    2. After deploying the application, open ?Validation?
    application in the
    admin console.
    3. Click ?Manage Modules?.
    4. Select ?EJB_1.jar and click on ?View Deployment Descriptor?.
    You can
    see EJB 2 reference is listed here. It is working as expected.
    5. Select ?EJB_2.jar? and click on ?View Deployment Descriptor?.
    You can
    see EJB 3 reference is missing here. This is where the issue.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server with J2EE 5 applications using       *
    *                  annotations for Enterprise JavaBean (EJB)   *
    *                  modules                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: An 'EJB' annotation referencing an      *
    *                      EJB in another jar within the           *
    *                      application is not resolved correctly.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    While resolving the reference for an EJB annotation, other EJB
    jars in the application may be opened and the deployment
    descriptors accessed. The loading of the additional deployment
    descriptors will caused annotation scanning to be done for
    them, which could lead to a recursive call to resolve an EJB
    annotation for the other deployment descriptor. In order to
    prevent an infinite loop, the recursive call to process the
    second EJB annotation does not allow a search in other EJB
    jars within the application to resolve an EJB reference. This
    prevents the EJB annotation reference to a third EJB jar from
    being resolved.
    

Problem conclusion

  • EJBMergeAction class was changed to allow multiple recursions
    while loading additional deployment descriptors but will
    prevent an infinite loop by not trying to load a deployment
    descriptor for which an EJBMergeAction process is active.
    
    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

    PM11652

  • 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-04-06

  • Closed date

    2010-05-27

  • Last modified date

    2010-05-27

  • 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 #: PM11652

Modified date: 27 May 2010