IBM Support

PI71210: DEPLOYMENT FAILS WHEN @EJB CONTAINS BEANNAME AND EJB DESCRIPTOR CONTAINS <LOOKUP-NAME>

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an EBJ descriptor contains an EJB reference element that
    includes a <lookup-name> element, and an @EJB annotation
    contains a beanName for the same reference a validation error
    occurs.
    
    ADMA0235E: A validation error occurred in task Mapping EJB
    references to enterprise beans. A lookup name <LOOKUP NAME> and
    EJB link <BEAN NAME> are specified for EJB reference
    <REFERENCE NAME> in module <EJB JAR FILE NAME>"
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server 9.0.0.1 who have applications with   *
    *                  EJBs                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Application deployment fails when an    *
    *                      @EJB annotation contains a "beanName"   *
    *                      attribute and the EJB descriptor        *
    *                      contains a reference specifying a       *
    *                      <lookup-name> element.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During processing of Java EE annotations, the application
    server merges information found in the annotations with the
    deployment descriptors.  The beanName attribute on the
    @EJB annotation is merged into the deployment descriptor as an
    <ejb-link> element on the EJB reference.  It is an error to
    have both an <ejb-link> element and a <lookup-name> element in
    the same EJB reference. This is an error in the merge
    processing.
    

Problem conclusion

  • The code has been modified so that it no longer writes the
    <ejb-link> into the EJB reference in the descriptor when a
    <lookup-name> element is already present.
    
    Note that this fix does not completely restore the behavior of
    WebSphere Application Server prior to version 9.0.0.1.  The
    problem is that the beanName attribute on an @EJB annotation
    is in conflict with the <lookup-name> on the EJB reference in
    the descriptor.  Prior to 9.0.0.1, beanName won the conflict.
    This resulted in <ejb-link> added to the merged descriptor
    instead of <lookup-name>.  In other words, the value on the
    annotation overrode the value in the descriptor.
    
    Values on descriptors must override values on annotations.
    With this fix, the value in the descriptor will win, meaning
    the EJB reference in the merged descriptor will contain
    <lookup-name> instead of <ejb-link>.
    
    To restore the old behavior, you need to remove <lookup-name>
    from the EJB reference in the ejb-jar.xml file before
    deploying the application.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 9.0.0.2.  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

    PI71210

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-25

  • Closed date

    2016-11-22

  • Last modified date

    2016-11-22

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021