PM81177: Agent calls and the clear API both hang when the AvailabilityException exception is expected for XIO transport.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • In a WebSphere eXtreme Scale configuration using the XIO
    transport, the clear() API or an agent call can hang. In
    situations where the clear() API or agent call should fail
    with an AvailabilityException because the data grid is not in a
    state where work can be done, the activity loses the exception
    and hangs.
    
    The AvailabilityException is expected when normal client
    transactions are used and the data grid is offline or in
    preload state. The AvailabilityException can also be expected
    when client preload is attempted while the data grid is in any
    state other than the preload state.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere eXtreme Scale customers with      *
    *                  applications that use the clear() API or    *
    *                  data grid agents in the same JVM as the     *
    *                  container server                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Agent calls or use of the clear API     *
    *                      can hang when AvailabilityException or  *
    *                      other exceptions occur.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When running in the same JVM, a clear() API call or an agent
    call will continue to wait for results even though an
    exception condition like AvailabilityException happens.
    

Problem conclusion

  • The clear() API or agent call returns the correct exception.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM81177

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-22

  • Closed date

    2013-02-08

  • Last modified date

    2013-02-08

  • 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

    WS EXTREME SCAL

  • Fixed component ID

    5724X6702

Applicable component levels

  • R860 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere eXtreme Scale

Software version:

860

Reference #:

PM81177

Modified date:

2013-02-08

Translate my page

Machine Translation

Content navigation