IBM Support

PI70110: EJB JAR METADATA TRANSACTIONATTRIBUTE MAY BE INCORRECT

Fixes are available

9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Application deployment processing generates metadata for
    modules, including EJB JARs, which are deployed.
    
    For example, see the files "ejb-jar_merged.xml" which are
    stored to the application deployment file sets under the
    configuration folder:
    PROFILE_HOME/config/cells/CELL_NAME/applications/APPLICATION_NAM
    E.ear.
    The "_merged.xml" files are stored in subdirectories beneath
    the application directory.
    
    The symptom of the problem is the placement of
    'trans-attribute' elements with incorrect values.
    
    For example, a business method of an EJB may specify a
    transaction attribute value of "NEVER":
    
    @TransactionAttribute(TransactionAttributeType.NEVER)
    
    While the generated "ejb-jar_merged.xml" can incorrectly have a
    value of 'Required':
    
    <trans-attribute>Required</trans-attribute>
    
    As a result of the incorrect transaction attribute value,
    bindings information for the EJB may be incorrectly generated.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: EJB bindings generated incorrectly      *
    *                      due to error in processing the          *
    *                      @TransactionAttribute annotation.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Application deployment processing merges metadata found in
    Java EE annotations with metadata found in deployment
    descriptors and saves the results into "merged" descriptors.
    For example, see the files named "ejb-jar_merged.xml" which are
    stored to the application deployment directories under the
    configuration folder:
    <PROFILE_HOME>/config/cells/<CELL_NAME>/applications/<APPLICATIO
    N_NAME>.ear.
    The "_merged.xml" files are stored in sub-directories beneath
    the application directory.
    The symptom of the problem is the generation of
    "trans-attribute" elements with incorrect values.
    For example, a business method of an EJB may specify a
    transaction attribute value of "NEVER", for example:
    @TransactionAttribute(TransactionAttributeType.NEVER)
    While the generated "ejb-jar_merged.xml" might incorrectly have
    a value of 'Required':
    <trans-attribute>Required</trans-attribute>
    As a result of the incorrect transaction attribute value,
    bindings information for the EJB may be incorrectly generated.
    

Problem conclusion

  • The code has been modified to properly process the
    @TransactionAttribute annotation.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.0.13, 8.5.5.12, 9.0.0.3.  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

    PI70110

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-04

  • Closed date

    2016-11-22

  • Last modified date

    2016-11-22

  • 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

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 October 2021