IBM Support

PH65081: Improve AsyncUpdate processing; Guard against malformed AIProtocolItemStream

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

  • A malformed AIProtocolItemStream, not containing a necessary
    AICompletedPrefixItem, was found persisted in the message store.
    
    When read at startup, this resulted in a malformed AIStream
    object being created with a null _completedPrefix field.
    
    As this field is used for synchronization in the object, this
    subsequently caused a number of NullPointerExceptions to be
    thrown during AsyncUpdate processing.
    
    As this processing was being handled in bundles of
    AsyncUpdates in a pseudo-transactional manner, this caused
    other updates (unconnected except for being scheduled at the
    same time) to be rolled back without any attempt at their
    successful operation.
    
    It was further observed that flaws in the handling of these
    exceptions might also lead to the diminution of the thread
    processing resources for the thread pool used by the
    AsyncUpdate processing, which could lead to slowdown in this
    area of the system.
    Such slowdown was observed.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of SIBus Messaging in IBM         *
    *                  WebSphere Application Server                *
    ****************************************************************
    * PROBLEM DESCRIPTION: FFDC NullPointerExceptions arising      *
    *                      from calls to methods on                *
    *                      com.ibm.ws.sib.processor.gd.AIStream;   *
    *                      messaging system slowdown.              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A malformed AIProtocolItemStream, not containing a necessary
    AICompletedPrefixItem, was found persisted in the message
    store.
    When read at startup, this resulted in a malformed AIStream
    object being created with a null _completedPrefix field.
    As this field is used for synchronization in the object, this
    subsequently caused a number of NullPointerExceptions to be
    thrown during AsyncUpdate processing.
    As this processing was being handled in bundles of
    AsyncUpdates in a pseudo-transactional manner, this caused
    other updates (unconnected except for being scheduled at the
    same time) to be rolled back without any attempt at their
    successful operation.
    It was further observed that flaws in the handling of these
    exceptions might also lead to the diminution of the thread
    processing resources for the thread pool used by the
    AsyncUpdate processing, which could lead to slowdown in this
    area of the system.
    Such slowdown was observed.
    It is likely that the frailties of the AsyncUpdate processing
    led to the malformed AIProtocolItemStream being persisted in
    the first place.
    

Problem conclusion

  • Guard code was added to identify, report and discard malformed
    AIProtocolItemStream retrieved from persistence, to avoid the
    creation of malformed AIStream objects.
    
    AsyncUpdate processing was modified to process each update
    within it own (local) transaction, thus avoiding any exception
    in one from causing others to be rolled back without running.
    
    AsyncUpdate processing was enhanced to prevent any
    exception/error thrown from an update from interfering with
    the thread pooling for this processing, thus avoiding the
    possibility of system degradation.
    
    The fix for this APAR is targeted for inclusion in fix packs
    8.5.5.28 and 9.0.5.24.
    For more information, see 'Recommended Updates for
    WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH65081

  • 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

    2025-02-02

  • Closed date

    2025-07-30

  • Last modified date

    2025-07-30

  • 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

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Document Information

Modified date:
30 July 2025