IBM Support

PK87402: HEURISTIC HAZARD AT THE SERVER LEVEL FOR A 6.0.2.X

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ***********************************************************
    
    Customer is getting warning since it looks like it is not valid
    for 6.0.2 from the traces.
    
    The problem is observed at at 6.0.2.31 WebSphere Application
    server.
    
    [5/21/09 18:36:59:359 IST] 0000000a TxServiceImpl W   WTRN0110W:
    ACCEPT_HEURISTIC_HAZARD is not a valid transaction service
    custom
    property
    ****************************************************************
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V6.0.2                               *
    ****************************************************************
    * 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.0.2.39.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    
    This APAR is the equivalent of APAR PK58217 which was raised
    against WebSphere Application Server v6.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK87402

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    60A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-05-27

  • Closed date

    2009-07-24

  • Last modified date

    2009-07-24

  • 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

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

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

Document Information

Modified date:
10 February 2022