PI45373: THE 'CMP-FIELD' ELEMENTS OF EJB DEPLOYMENT DESCRIPTORS ARE IGNORED.

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.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Enterprise Java Bean (EJB) processing ignores 'cmp-field'
  elements of Container Managed Persistence (CMP) beans.
  
  When a new CMP is created, WebSphere Application Server should
  be cycling through the CMP field (<cmp-field>) elements defined
  in the ejb-jar.xml file and reinitializing them to null (or the
  primitive equivalent).
  
  Instead, it looks like bean instances are being retrieved from
  the pool (which is okay), but no field initialization is
  occurring, meaning that we end up with garbage data from the
  previous instance of the CMP.  This is especially problematic
  with the fields that store key information for linked CMPs.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Enterprise Java Bean (EJB) processing   *
  *                      ignores CMP fields of Container         *
  *                      Managed Persistence (CMP) beans.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When creating new Container Managed Persistence (CMP) beans,
  the CMP fields of the beans should be reinitialized to null or
  to the equivalent primative value.  CMP fields are defined
  using "cmp-field" elements in the EJB deployment descriptor,
  ejb-jar.xml.
  Reinitialization of CMP fields is not being performed. CMP
  fields are left with data from previous instances of the
  enclosing CMP beans.
  Retention of data from previous instances of CMP beans is
  especially problematic for CMP fields which store key
  information for linked CMP beans.
  

Problem conclusion

• The problem occurred because the API used to retrieve CMP
  field metadata returned the wrong metadata.  The result was the
  return of an empty collection of CMP field metadata.  This
  meant that EJB processing would ignore CMP field
  initialization steps when creating new CMP beans.
  
  The problem was resolved by changing the API implementation
  to return the correct metadata.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.7.  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