PM86284: An EJB defined by annotation is ignored

8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

APAR status

• Closed as program error.

Error description

• WASAxis2Descr WSWS7150E: The
  system could not build a runtime configuration for the
  abc application module because of the following error:
  com.ibm.ws.websvcs.exception.DeploymentException:
  WSWS7149E: The def ejb-link value for the
  {bean-name}...Bean Enterprise JavaBeans Web service
  implementation class did not correspond to an enterprise
  bean defined in the ejb-jar.xml file for the abc module.
  When there are different values in @stateless and in the
  ejb-jar.xml deployment descriptor file, then there can be an
  error where an EJB defined via annotation is not created if
  there is another EJB already defined for the same class.
  

Local fix

• Change the spelling of the bean name so that it is the same in
  both locations (@stateless and in the ejb-jar.xml deployment
  descriptor file). Or, define it just once using either an
  annotation or the ejbjar.xml.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server using J2EE annotations to define     *
  *                  EJBs                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: If there are two EJBs defined using     *
  *                      the same class, one in the              *
  *                      ejb-jar.xml and the second by           *
  *                      annotation on the class, the EJB        *
  *                      defined by the annotation will not be   *
  *                      created.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The current annotation processing only allows one EJB to be
  defined for a specific class.
  The conflict occurs if there are two EJBs defined:
  - ejbA, defined in an ejb-jar.xml using a specified ejb-class.
  - ejbB, defined as an annotation in the same EJB class as ejbA.
  This results in an ejb-jar_merged.xml containing only a
  definition for ejbA.
  According to the EJB specification, there can be multiple EJBs
  defined using the same class as long as the EJB names are
  different.
  

Problem conclusion

• Annotaion processing has been changed to allow multiple EJBs
  defined for a single class if the names are different.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.1.  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 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

• R850 PSY

     UP