PM98652: EJB INJECTION CLASSES CHANGE DURING AN APPLICATION UPDATE

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
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

• An application that uses EJB injection can be deployed
  fine.
  
  When the application is updated, the list of injection
  classes unexpectedly changes and the application no longer
  runs.
  
  Issue is related to how IBM Metadata in this scenario
  (ejb-in-war scenario) is saved.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server using Java EE Web Modules            *
  *                  that contain EJBs.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: The list of injection classes for a     *
  *                      web module is updated by the            *
  *                      ejb-in-war annotation scan.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  There are potentially two annotation scans which are done for
  a web module. One scan is done to merge annotation information
  into the web.xml and another is done to merge annotation
  information into the ejb-jar.xml. These scans each run against
  a different set of classes contained in the Web Application
  Archive (WAR). Each of these scans also generates a list of
  module classes which is cached for use by other components,
  but they are both cached in the same location. As a result,
  the list of module classes generated by the web.xml scan is
  overlaid if a later scan is done to merge the ejb-jar.xml.
  The Webcontainer uses the list of module classes as its list
  of injection classes and when the contents of the list is
  changed, it results in the application failing to start.
  

Problem conclusion

• The annotation scan process has been changed to use a separate
  list for storing module classes for each scan.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.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

• R850 PSY

     UP