IBM Support

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

Subscribe

You can track all active APARs for this component.

 

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 number

    PI52391

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-11-12

  • Closed date

    2016-02-23

  • Last modified date

    2016-02-23

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
16 October 2021