PM42611: CDI problems with BeanManager and certain CDI API calls.

8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
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

• This APAR addresses the following errors:
  
     * The BeanManager instance looked up through JNDI is not
  serializable, which could lead to NotSerializableExceptions for
  beans with passivating scopes. BeanManagers injected with
  @Inject do not have this same problem.
  
      * CustomInterceptors and custom bean classes added using
  the API might be ignored due to hashCode collisions.
  
      * Lifecycle events, such as ProcessInjectionTarget get
  fired with the wrong generic types which could lead to
  listeners not being called.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Version    *
  *                  8.0 users of Contexts and Dependency        *
  *                  Injection (CDI).                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: CDI problems with BeanManager and       *
  *                      certain                                 *
  *                      CDI API calls.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This APAR resolves the following problems:
  * The BeanManager instance looked up through JNDI is not
  serializable, which could lead to NotSerializableExceptions for
  beans with passivating scopes. BeanManagers injected with
  @Inject do not have this same problem.
  * CustomInterceptors and custom bean classes added using the
  API might be ignored due to hashCode collisions.
  * Lifecycle events, such as ProcessInjectionTarget get fired
  with the wrong generic types which could lead to listeners not
  being called.
  

Problem conclusion

• The container has been updated to resolve these issues.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.1.  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

• R800 PSY

     UP