IBM Support

PM63327: PROVIDE AN SPI FOR EVENT SEQUENCING LOGIC TO CONTROL WHEN SIBUS DESTINATION DELIVERY COUNT IS INCREMENTED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Add an API to control incrementing the redelivery count of the
    message when message is unlocked in a consumer session.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider for *
    *                  IBM WebSphere Application Server            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Add an API to control incrementing      *
    *                      the redelivery count of the message     *
    *                      when message is unlocked in a           *
    *                      consumer session.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    * Stack product users need the ability to control when the
    redelivery count is incremented for a message and ensure that
    the order on queue is always preserved. Currently, when the
    application or SCA component rolls back the message, the
    redeliveryCount of the message is automatically incremented
    * Retries or rollback occur when a client uses an asynchronous
    invocation pattern and a ServiceRuntimeException is thrown by
    the service provider. Asynchronously client receive re-tries
    as a result of the settings in the SIBus destination. It uses
    the attribute "Maximum failed delivers per message", with the
    current default value being 5. When set to 1 then no retries
    will occur. When the message has reached maximum redelivery
    count, the message is moved to exception destination.
    * The requirement is that, stack product users need the
    ability to control incrementing the redelivery count of the
    message when message is unlocked in a consumer session and
    also needs that all the locked messages are unlocked in
    sequence.
    

Problem conclusion

  • * A new method unlockAll(boolean incrementLockCount) is
    introduced in the com.ibm.wsspi.sib.core.ConsumerSession
    
      public void unlockAll(boolean incrementLockCount)
        throws SISessionUnavailableException,
    SISessionDroppedException,
               SIConnectionUnavailableException,
    SIConnectionDroppedException,
               SIResourceException, SIConnectionLostException;
    
    * Consumers will invoke this method to unlock all the messages
    in the consumersession
    * At the server side first the consumer session is stopped
    temporarily and messages are unlocked in sequence
    * Once all the messages are unlocked only then is the consumer
    session started so that messages flow from server to client
    
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.4 and 8.5.0.1.  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

    PM63327

  • Reported component name

    WAS SIB & SIBWS

  • Reported component ID

    620800101

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-04-26

  • Closed date

    2012-08-28

  • Last modified date

    2012-08-28

  • 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

    WAS SIB & SIBWS

  • Fixed component ID

    620800101

Applicable component levels

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

Document Information

Modified date:
28 October 2021