PI52391: BeanManger.equals can not distingiush between two BeanManagers f or the same module after a restart

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

• Re-deploying Enterprise application which uses CDI may see
  failure as indicated below in Liberty 8.5.5.7
  
  [10/21/15 8:40:31:195 EDT] 0000005e
  com.ibm.ws.webcontainer.util.ApplicationErrorUtils
  E
  SRVE0777E: Exception thrown by application class
  'javax.faces.webapp.FacesServlet.service:230'
  javax.servlet.ServletException: javax.el.ELException:
  org.jboss.weld.exceptions.UnsatisfiedResolutionException:
  WELD-001308:
  Unable to resolve any beans for Type: class
  cdi.test.TestBean;
  Qualifiers: []
  at
  javax.faces.webapp.FacesServlet.service(FacesServlet.java:23
  0)
  at
  com.ibm.ws.webcontainer.servlet.ServletWrapper.service(Servl
  etWr
  apper.ja
  va:1287)
  

Local fix

• restart Liberty server
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile - Contexts and       *
  *                  Dependency Injection (CDI)                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: A cache was not cleaned during a        *
  *                      restart, as a result a module could     *
  *                      have multiple BeanManagers and          *
  *                      BeanManger.equals could not distingiush *
  *                      between them.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A cache was not cleaned during a restart, as a result a module
  could have multiple BeanManagers and BeanManger.equals could not
  distingiush between them.
  

Problem conclusion

• Code was was refactored so relevent objects were created per
  deployment rather than per runtime.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.9.  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

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R855 PSY

     UP