Clovertech

Route Messages Problem

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Route Messages Problem

  • Creator
    Topic
  • February 20, 2009 at 7:22 pm #50654
    Garrett Fletcher
    Participant

      Hello,

      Let me first describe our setup. We have an inbound thread that sends to 5 Outbound Threads. In the Route Messages Tab we have one “Transaction ID” (Folder) with the 5 route detalis under it.

      Our problem is we had one of the procs in one of the “details” throw an error. That caused the message to not send to any of the outbound threads specified in the different “details”.

      My question is how are the procs related to the “Transaction IDs” and the “details”? And if the proc errored when it was in a seperate transaction folder would it have affected the details in the different transaction folders?

      Can the procs in one detail affect messages in another detail?

      Thanks in advance.

      Garrett

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • February 23, 2009 at 6:28 pm #66989
        Vince Angulo
        Participant

          We first ran into this back when we were on 3.7 or 3.8 — not sure of the “why” — it might be because all the outbounds are in the same process.  

          The workaround we picked up at a user group conference, instead of routing directly to the outbound threads, to place a “pass” thread in front of each outbound thread, with the pass thread and outbound thread in a distinct process.  We route raw from the inbound to the pass threads and do the procs and xlates in the single route between the pass threads and the outbounds.  That way errors in one process don’t affect other target processes/threads.

        • February 23, 2009 at 6:36 pm #66990
          Garrett Fletcher
          Participant

            Thank you for your advice, Vince. We will look into doing that.

            Garrett

          • February 23, 2009 at 6:36 pm #66991
            Rob Abbott
            Keymaster

              Garrett this is working as designed.  CL was designed to route messages as an “atomic” operation.  If one detail fails for a trxid then they all fail.  The idea was to keep destination systems in sync and make it easier to recover from this by resending from the inbound SMAT.

              We have had some discussion around making this behavior an option in a future release (e.g. fail all as it is today, or just fail the one detail)

              Rob Abbott
              Cloverleaf Emeritus

            • February 23, 2009 at 6:37 pm #66992
              Garrett Fletcher
              Participant

                Thank you, Rob. It is good to know that our system is working as it is designed and we do not have a problem.

                Garrett

            • Author
              Replies
            Viewing 3 reply threads
            • The forum ‘Cloverleaf’ is closed to new topics and replies.