Cloverleaf Xlate Routing Error Question

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Cloverleaf Xlate Routing Error Question

  • Creator
    Topic
  • #54058
    Robert Milfajt
    Participant

      Back in the 90s when I got my Cloverleaf Level I certification we were taught that if for some reason there is an error in an the xlate thread of a process (either in an Xlate or TCL call out from pre/post TPS) that the message that caused the error would not be routed to all other destinations.  This would be for Clovelreaf 5.7 on AIX.

      My question is that is it all details on a the route with the error, or all Xlate (not Raw) details within that route, or all details after the detail that errored out within the route?  Or does it cross over to other routes?

      Just trying to figure out how this all works for debugging purposes.

      Thanks,

      Bob

      Robert Milfajt
      Northwestern Medicine
      Chicago, IL

    Viewing 10 reply threads
    • Author
      Replies
      • #80016

        As soon as there is an error, the message stops moving through the engine and is moved to the error database. In CIS 6.0, an option was added to change this behavior if desired (you can opt to allow the message to continue moving through the engine).

        -- Max Drown (Infor)

      • #80017
        Robert Milfajt
        Participant

          Thanks Max.  So any details processed to that point get through to the destinations, and any after that point do not.  That makes sense based on what I’m seeing.

          Robert Milfajt
          Northwestern Medicine
          Chicago, IL

        • #80018

          Robert Milfajt wrote:

          Thanks Max.

          -- Max Drown (Infor)

        • #80019
          Peter Heggie
          Participant

            I thought all of the ‘destination’ messages that made it through a particular detail were held in an internal queue until all of the other destinations also made it through successfully, and then when all were gathered, all were then released to the outbound threads. But if there was an error in any of them, then none of them were released to the outbound queue?

            Is that similar to the new functionality of specifying particular destinations for a message resend, where you can see all of the route details being executed (by seeing the debugging messages you put in), but at the end, only the destinations you specified are actually getting the outbound messages?

            Peter Heggie

          • #80020
            James Cobane
            Participant

              Max,

              Where is this configuration option (in 5.8+) to “change this behavior if desired (you can opt to allow the message to continue moving through the engine)”?

              Thanks,

              Jim Cobane

              Henry Ford Health

            • #80021

              The setting is located under Route properties. In 6.0, double click on the route. The setting is called “Remove all messages when any route detail fails”. It can be toggled on and off.

              I don’t see that option in 5.8.5, so I guess it was added in 6.0.

              -- Max Drown (Infor)

            • #80022

              Peter Heggie wrote:

              I thought all of the ‘destination’ messages that made it through a particular detail were held in an internal queue until all of the other destinations also made it through successfully, and then when all were gathered, all were then released to the outbound threads. But if there was an error in any of them, then none of them were released to the outbound queue?

              Is that similar to the new functionality of specifying particular destinations for a message resend, where you can see all of the route details being executed (by seeing the debugging messages you put in), but at the end, only the destinations you specified are actually getting the outbound messages?

              I’m researching this. I’ll get back to you asap.

              -- Max Drown (Infor)

            • #80023
              James Cobane
              Participant

                Thanks. I wasn’t able to find it in 5.8.5, so that’s why I asked.

                Jim Cobane

                Henry Ford Health

              • #80024

                Here’s some more info from R&D.

                Need to select the check box in all of the routes. Otherwise, the message will go the destination thread.

                static route to thread 1 and thread2        checkbox=y

                -- Max Drown (Infor)

              • #80025
                Steve Pringle
                Participant

                  I understand the 2nd example:

                  Static route to thread 1 and thread2        checkbox=y

                • #80026
                  Robert Milfajt
                  Participant

                    BTW, it appears that when you convert from a version that doesn’t have the functionality to one that does, the default is to check the box, i.e., drop the messages.

                    Thank you Max for the info.

                    Robert Milfajt
                    Northwestern Medicine
                    Chicago, IL

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