IBM Support

PK58217: WTRN0063E OCCURS WITH LAST PARTICIPANT SUPPORT ENABLED WHEN SINGLE-PHASE RESOURCE IS USED IN A SYNCHRONIZATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In WebSphere Application Server V6.1, a WTRN0063E error may
    occur when a single-phase (non-XA) resource is enlisted in a
    transaction with other two-phase (XA) resources even when Last
    Participant Support (LPS) is enabled for the application:
    .
    WTRN0063E: An illegal attempt to commit a one phase capable
    resource with existing two phase capable resources has occurred.
    .
    This occurs when a message driven bean tries to use the single-
    phase resource while doing a synchronization.  The transaction
    service does not allow LPS during a synchronization.  This is
    because the transaction service calls the synchronizations in
    the order in which they are enlisted, and the EJB
    synchronization will always be enlisted first; the application
    cannot specify the ordering.
    

Local fix

  • Use a two-phase capable (XA) resource instead of a single-phase
    resource, or use the ExtendedJTATransaction interface to
    register for synchronization callbacks.  Synchronizations
    registered in this way are guaranteed to be called before other
    types of synchronizations.  If using the ExtendedJTATransaction
    interface, the fix for APAR PK41846 must be applied.  The fix is
    included in Fix Pack 9 (V6.1.0.9) and above.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IBM WebSphere Application Server V6.1    *
    *                 users                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: An WTRN0063E (An illegal attempt to     *
    *                      commit a one phase capable resource     *
    *                      with existing two phase capable         *
    *                      resources) error may occur when a       *
    *                      single-phase (non-XA) resource is       *
    *                      enlisted in a transaction with other    *
    *                      two-phase (XA) resources even when      *
    *                      Last Participant Support (LPS) is       *
    *                      enabled for the application.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A message driven bean was attempting to use the single-phase
    resource as part of a customer-supplied mediation during
    beforeCompletion() processing.  Mediations are enlisted with
    the transaction as synchronizations, but the LPS parameter
    setting cannot be detected by the transaction service while
    processing this synchronization.  This is because the
    transaction service calls the synchronizations in the order
    in which they are enlisted, and the EJB synchronization will
    always be enlisted first - when the EJB synchronization
    completes, the EJB environment (of which the LPS setting is
    a part) is removed, preventing subsequent processing from
    detecting the LPS setting. The application cannot specify
    the ordering of synchronizations.
    

Problem conclusion

  • Optionally provide server-wide support for LPS. This
    enables LPS for all applications that run on the application
    server. This action is controlled by Transaction Service
    custom property ACCEPT_HEURISTIC_HAZARD.
    
    To enable server-wide LPS, complete the following steps in the
    administrative console:
    
    In the administrative console, click Servers > Application
    Servers > server_name
    This action displays the properties of the application server
    in the content pane.
    Under Container Settings, expand Container Services and click
    Transaction Service to display the properties page for the
    transaction service.
    Under Additional Properties click Custom Properties.
    On the Custom Properties page, click New.
    Type ACCEPT_HEURISTIC_HAZARD in the Name field and type TRUE in
    
    the Value field.
    Click Apply or OK.
    Click Save to save your changes to the master configuration.
    Restart the server.
    
    If this custom property is not set, or is set to FALSE, LPS
    behaviour will be determined by the LPS setting on the
    application.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.1.0.17. 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

    PK58217

  • Reported component name

    WEBSPH APP SERV

  • Reported component ID

    5724J0800

  • Reported release

    61W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-12-13

  • Closed date

    2008-03-20

  • Last modified date

    2008-03-20

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • TRANS
    

Fix information

  • Fixed component name

    WEBSPH APP SERV

  • Fixed component ID

    5724J0800

Applicable component levels

  • R60A PSN

       UP

  • R60H PSN

       UP

  • R60I PSN

       UP

  • R60P PSN

       UP

  • R60S PSN

       UP

  • R60W PSN

       UP

  • R60Z PSN

       UP

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z 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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021