IBM Support

IC98491: OUTBOUND AS2ASYNCMDN PROCESS IS KICKED OFF TO SEND, BUT DOES NOT RECEIVE RETURNING MDN AND KEEPS ON RETRYING.

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

  • Customer's outbound AS2AsyncMDN process is kicked off to send
    data, but, it does not receive returning MDN and continues its
    retry logic. On its first send, it waits 5 minutes then
    checks for the return MDN. If not, it checks again in another
    5 minutes for a total of 5 times. After all the waiting and if
    still no MDN returned, it kicks off another process to send data
    again, and repeats the above wait process.
    In a normal situation, in 25-30 minutes is all it has to wait
    until the next send process is invoked. But, since the PMR was
    opened, customer noticed that it took almost 2 hours for the
    resend to occur, thus, the resends are taking longer and longer
    for resending the same data. At this time, there are 7000+ BP in
    the wait queue.
    

Local fix

Problem summary

  • Users Affected:
    All
    
    Problem Description:
    Outbound AS2AsyncMDN process is kicked off to send but
    does not receive the returning MDN.
    In rare cases, under heavy load, where a BP reschedule keeps
    sending a BP to another node's waitQueue (Queue 0), BP's could
    keep bouncing around in various node waitqueues when nodes
    were load balancing.
    
    Platforms affected:
    All
    

Problem conclusion

  • Resolution Summary:
    A code fix has been provided.
    
    Delivered In:
    5020500_6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC98491

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    510

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-12-24

  • Closed date

    2015-02-16

  • Last modified date

    2015-10-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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

  • R525 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
30 October 2015