IBM Support

PI14034: PROBLEM HANDLING CDI INTERCEPTORS

Fixes are available

8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
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.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
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.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The expected behaviour according to the Interceptor
    specification is that one should be able to intercept the
    lifecycle method in the target bean annotated @PostConstruct.
    But testing indicates that the @PostConstruct annotated method
    is treated as a normal @PostConstruct method on a CDI managed
    bean.  This is caused by a problem with the order that
    lifecycle interceptors are fired for a target bean.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server Full       *
    *                  Profile versions 8.0 and 8.5 and Liberty    *
    *                  Profile version 8.5 users of Contexts       *
    *                  and Dependency Injection (CDI).             *
    ****************************************************************
    * PROBLEM DESCRIPTION: Lifecycle callback interceptor          *
    *                      methods defined on target class fire    *
    *                      in the wrong order for CDI managed      *
    *                      beans                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The "Interceptors 1.1" specification defines the rules
    governing invocation order when multiple callback interceptor
    methods are defined for a single lifecycle event on a target
    class. More specifically, when a lifecycle callback
    interceptor method is defined on the target class itself, that
    method should be invoked after all other interceptor methods
    for that class have been invoked.
    However, the CDI implementation invokes lifecycle callback
    interceptor methods defined on the target class before any
    other interceptor methods, leading to incorrect invocation
    order.
    

Problem conclusion

  • The CDI implementation was modified to invoke interceptor
    methods in the correct order. To enable the fix for this APAR,
    the new custom property
    "com.ibm.ws.webbeans.invokeInterceptorMethodOnTargetClassLast"
    must be set to true (default=false) in the
    META-INF/openwebbeans/openwebbeans.properties file of a bean
    archive.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.9 and 8.5.5.3.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    
    In addition, please refer to URL:
    http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack PTF information.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI14034

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-03-19

  • Closed date

    2014-05-01

  • Last modified date

    2014-05-13

  • 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 FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022