IBM Support

PM79511: METHODS NOT BEING RECOGNIZED AS BUSINESS METHODS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using the @Asynchronous annotation, the following warning
    may be seen in the SystemOut.log:
    
    com.ibm.wsspi.amm.validate.ValidationException: CWWAM1101E: In
    class xxxx.xxxx.xxxx the method asyncMethod is
    annotated with @Asynchronous but must be applied to a business
    method of a bean class or to a business method of a Local/Remote
    business interface.
     at
    com.ibm.ws.amm.validate.ejb.AsynchronousValidator.validateMethod
    Annotation(AsynchronousValidator.java:99)
     at
    com.ibm.ws.amm.validate.ejb.AsynchronousValidator.validate(Async
    hronousValidator.java:61)
    
    The cause of the warning is that the methods of classes that
    implement local or remote business interfaces are not being
    recognized as business methods.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Methods of classes that implement       *
    *                      local or remote business interfaces     *
    *                      are not being recognized as business    *
    *                      methods.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The logic to determine "business" methods is incorrect and
    returns a false determination when the method being evaluated
    implements a business method from an interface.
    

Problem conclusion

  • The logic to determine if a method is a "business" method has
    been changed to correctly identify an implementing method as a
    business interface.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.0.6.  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

    PM79511

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-12-19

  • Closed date

    2013-01-25

  • Last modified date

    2013-01-25

  • 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 APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R800 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:
29 October 2021