Clovertech

Getting ACKs in Error Database

› Clovertech Forums › Cloverleaf › Getting ACKs in Error Database

Tagged: 

  • Creator
    Topic
  • April 20, 2026 at 1:17 pm #122444
    Michael Brande
    Participant

      Hey everyone,

      We occasionally get ACKs from systems that land in our Error DB. Does anyone know why this occurs or how to stop it?

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • April 20, 2026 at 1:20 pm #122446
        Jason Russell
        Participant

          Are you using the default recover (cl_check_ack) tcl script to look at the ACKs?

          Are they actual ACKs (AA/CA) or ACKs with Errors (AE/CE)

        • April 20, 2026 at 1:35 pm #122449
          James Cobane
          Participant

            If you aren’t handling the replies via a proc or actually routing them, then they will hit the error database.  Also, do you have ‘Outbound Only’ checked on ‘Inbound’ tab of the thread?  If you don’t, if a reply message comes in when the connection is not expecting a reply, then it will hit the error database as well.

            Hope that helps.

            Jim Cobane – Henry Ford Health

          • April 20, 2026 at 2:46 pm #122450
            Michael Brande
            Participant

              These are normal ACKS MSA|AA. These are routed and work 99% of the time. It’s just this odd this where 1% of the time (and not for all interfaces but only for certain vendors). Was wondering if anyone else saw anything like that.

              • April 20, 2026 at 4:59 pm #122451
                Jim Kosloskey
                Participant

                  If an unsolicited reply is received, it can end up in the recovery DB. This can happen when there is a timing issue as a result of the timeout value being exceeded.  Sometimes during high volume, the vendor cannot keep up and upping the timeout value may resolve. The 1% occurrence lends itself to this theory.

                  email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.

              • April 21, 2026 at 8:40 am #122453
                Jason Russell
                Participant

                  So a few things I have found:

                  If you have a 1:1 message:ack ratio (synchronous), you should have the ‘outbound only’ checkbox checked and everything routed via “route replies”. You should also have the “await replies” checkbox checked, with no proc (if you’re not specifically handling them) This treats all messages as a reply message. Anything that is NOT sent as a reply is thrown away and ignored.

                  If you do NOT have a 1:1 message:ack ratio (asynchronous) , you essentially do the opposite. You uncheck await replies and outbound only, and you route them via the “route message” tab (not the replies) and treat them as a data message. This ensures that all messages that are sent back in are routed.

                  I have a feeling with the way you’re describing it, it is as Jim says and you’re getting errant ACKS (delayed or whatnot), and you want option 1. That /should/ resolve the issue.

              • Author
                Replies
              Viewing 3 reply threads
              • You must be logged in to reply to this topic.