IBM Support

PM85886: INTERCEPTOR ANNOTATION LOGS ERROR UNLESS PLACED ON INTERCEPTOR OR BEAN CLASS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Deployment of a module containing a class annotated with
    @AroundInvoke, @PostConstruct, or @PreDestroy when the class
    containing the annotation is not an EJB class and is not marked
    as an Interceptor class, will incorrectly generate a "Could not
    locate target class" error displayed to server logs. The
    annotations should be allowed when the target class is not an
    EJB class and is not marked as an interceptor.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using classes annotated with         *
    *                  Lifecycle annotations.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Deployment of a class containing        *
    *                      @AroundInvoke, @PostConstruct,          *
    *                      or @PreDestroy and which is not an EJB  *
    *                      or Interceptor class incorrectly        *
    *                      displays error "Could not locate        *
    *                      target class".                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When deploying an application which contains a class that uses
    a Lifecycle annotation -- @AroundInvoke, @PostConstruct, or
    @PreDestroy -- the error message "Could not locate target
    class" is displayed when the annotation does not target an EJB
    class and does not target an Interceptor class.
    The message is incorrect to display because a Lifecycle
    annotation is permitted to target a class which is neither
    an EJB class nor an Interceptor class.  The case occurs
    infrequently, but is possible, for example, when using
    third party utility code, which may place Lifecycle
    annotations on unused utility classes.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PM85886

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-03-29

  • Closed date

    2013-06-12

  • Last modified date

    2013-06-12

  • 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

  • R850 PSY

       UP

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

Document Information

Modified date:
11 January 2022