PM47359: COM.IBM.EJS.CONTAINER.EJBCONFIGURATIONEXCEPTION FOR EJB 3.1 MDB

8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• [8/23/11 8:27:38:530 EDT] 00000019 WASEJBMDOrche E
  CNTR0144E: The Enterprise JavaBeans (EJB) binding with the
  XXX Java Naming and Directory Interface (JNDI) name has a
  jca-adapter stanza that does not contain an
  activation-spec-binding-name value.
  [8/23/11 8:27:38:530 EDT] 00000019 AbstractEJBRu E   WSVR0040E:
  addEjbModule failed for XXX_EJB.jar
  com.ibm.ejs.container.EJBConfigurationException: The XXX
  message-driven bean (MDB) does not have a corresponding binding
  in the binding file.
  at
  com.ibm.ws.metadata.ejb.WASEJBMDOrchestrator.processMessageDrive
  nBeanBinding(WASEJBMDOrchestrator.java:341)
  
  occurs when starting an MDB application with an EJB 3.1 MDB.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server V8.0 users *
  *                  of listener ports for Message-Driven Beans  *
  *                  (MDBs) in Enterprise Java Beans (EJB)       *
  *                  version 3.0 modules                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: The EJB container issues the            *
  *                      CNTR0144E message when a listener       *
  *                      port binding is used.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The logic for handling MDB bindings failed to consider that
  activation-spec-binding-name can be omitted when listener
  ports are used.
  

Problem conclusion

• The logic for handling MDB bindings was updated to allow
  activation-spec-binding-name to be omitted.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.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 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

• R800 PSY

     UP