App Connect

App Connect

Join this online user group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  Retry mechanism in ACE v11 with file nodes

    Posted Tue February 09, 2021 07:45 AM
    Hi,

    In the ACE v11 file input node we have a tab for enabling the retry in case of failure with retry threshold and short retry interval.

    I have tested the behavior and it works fine, however, each message is treated as a separate transaction. So there is no way to know which one is the original message vs which one is the retry message. I don't see any headers which indicate this retry count.

    During processing, is there a way to identify what is the retry count so that the original message vs the retry messages can be linked with a uniqueue Transaction id?

    Appreciate help from the experts here.

    Regards,
    Saha

    ------------------------------
    Prosanta Saha
    ------------------------------


  • 2.  RE: Retry mechanism in ACE v11 with file nodes

    Posted Fri May 24, 2024 09:58 AM

    Hi, 

    As I see, There is no property to identify message is original message or retry message. One e of the alternative solution is using "CURRENT_TIMESTAMP" . First timestamp value is original message and later timestamps can be considered as retried messages.

    Regards:

    Ravi.



    ------------------------------
    RAVI BABU KALVA
    ------------------------------

    Original Message


  • 3.  RE: Retry mechanism in ACE v11 with file nodes

    Posted Mon May 27, 2024 08:37 AM

    Hello!

    You can do two things, either using transactionID or setting a retryCount. Like this

    Using retryCount
    -- Check if RetryCount property exists
    DECLARE retryCount INTEGER COALESCE(InputLocalEnvironment.Destination.File.RetryCount, 0);

     
    -- Increment RetryCount
    SET retryCount = retryCount + 1;

     
    -- Store the updated RetryCount in LocalEnvironment
    SET OutputLocalEnvironment.Destination.File.RetryCount = retryCount;

    OR

    Setting transactionID

    -- Generate a unique transaction ID 
    DECLARE transactionID CHARACTER;
    SET transactionID = UUIDASCHAR;

     
    -- Add the transaction ID to the message as a property
    SET OutputRoot.Properties.TransactionID = transactionID;

    Regards,

    Kjetil Svihus



    ------------------------------
    Kjetil Svihus
    ------------------------------

    Original Message