IBM Support

PM03702: PROCESSING A MDB THAT HAS A TIMEOUT CALLBACK DOESN'T DEFINE A TRANSCATIONATRIBUTE ANNOTATION, A VALIDATIONEXCEPTION WILL OCCUR

Fixes are available

7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • if an ejb has the javax/ejb/TransactionManagement attribute with
    a CONTAINER value and the timerService method is present and
    does not have the TranslationAttributeannotation, then
    the activateTimer method does not have the
    @TransactionAttribute annotation, as the exception below:
    
    com.ibm.wsspi.amm.validate.ValidationException: the
    message-driven bean
    timeout callback method activateTimer is annotated with
    @TransactionAttribute but contains invalid values.  REQUIRES,
    REQUIRES_NEW, or NOT_SUPPORTED is expected;
            at
    com.ibm.ws.amm.merge.ejb.TransactionAttributeMergeAction.validat
    eTimeout
    Callbacks(TransactionAttributeMergeAction.java:869)
            at
    com.ibm.ws.amm.merge.ejb.TransactionAttributeMergeAction.validat
    eSession
    BeanMethod(TransactionAttributeMergeAction.java:812)
            at
    com.ibm.ws.amm.merge.ejb.TransactionAttributeMergeAction.validat
    e(Transa
    ctionAttributeMergeAction.java:761)
            at
    com.ibm.ws.amm.merge.ejb.TransactionAttributeMergeAction.merge(T
    ransacti
    onAttributeMergeAction.java:142)
            at
    com.ibm.ws.amm.AnnotativeMetadataManagerImpl.merge(AnnotativeMet
    adataMan
    agerImpl.java:156)
            at
    com.ibm.ws.amm.commonarchive.AnnotationsProcessorImpl.merge(Anno
    tationsP
    rocessorImpl.java:115)
    
    
    
    A review of the source for "TransactionAttributeMergeAction"
    shows an explicit test (in validateTimeCallback) which requires
    that the value of the annotation is one of REQUIRES,
    REQUIRES_NEW, or NOT_SUPPORTED. However, "REQUIRES" is a typo,
    the correct value is "REQUIRED". The annotation processing
    assigns a default attribute value of "REQUIRED".
    

Local fix

  • <NONE>
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server 7.0 using enterprise beans.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: ValidationException is thrown for       *
    *                      message-driven bean timeout callback    *
    *                      method activateTimer during             *
    *                      annotation processing.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The correct transaction attribute values for timeout callback
    method are REQUIRED, REQUIRES_NEW, or NOT_SUPPORTED. REQUIRED
    is the default value. The annotation processing validation
    code incorrectly checks for REQUIRES, instead of REQUIRED.
    
    This causes the following exception:
    com.ibm.wsspi.amm.validate.ValidationException: the
    message-driven bean timeout callback method activateTimer is
    annotated with @TransactionAttribute but contains invalid
    values.  REQUIRES, REQUIRES_NEW, or NOT_SUPPORTED is expected;
    at
    com.ibm.ws.amm.merge.ejb.TransactionAttributeMergeAction.validat
    eTimeout
    Callbacks(TransactionAttributeMergeAction.java:869)
    at
    com.ibm.ws.amm.merge.ejb.TransactionAttributeMergeAction.validat
    eSession
    BeanMethod(TransactionAttributeMergeAction.java:812)
    at
    com.ibm.ws.amm.merge.ejb.TransactionAttributeMergeAction.validat
    e(Transa
    ctionAttributeMergeAction.java:761)
    

Problem conclusion

  • Code changes have been made to fix this problem. The
    validation now checks for REQUIRED, REQUIRES_NEW, or
    NOT_SUPPORTED, instead of REQUIRES, REQUIRES_NEW, or
    NOT_SUPPORTED.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.11.  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

    PM03702

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    61W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-12-16

  • Closed date

    2010-01-29

  • Last modified date

    2010-01-29

  • 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

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021