Clovertech

Testing for a routing failure?

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Testing for a routing failure?

  • Creator
    Topic
  • March 19, 2015 at 8:42 pm #54622
    Mark Brown
    Participant

      We discovered a problem where messages weren’t being routed because the sending system is somehow goobering the message type in MSH:8.

      The bosses are wanting an alert if nothing comes across after a couple of days. However, the receiving thread gets messages from other sources, so that can’t be tested and the sending system is sending to some other systems with a static route so they never have an issue.

      Oddly no one seems interested in fixing the offending system, so I put a tcl proc in place that fixes the problem on the engine side and now the messages are being routed.

      My question is, is there any way to set up an alert to notice if these particular messages aren’t  making it to the designated thread, if that makes sense?

      CL6.01, Windows 2008

    • Creator
      Topic
    Viewing 2 reply threads
    • Author
      Replies
      • March 20, 2015 at 12:11 am #82255
        Jim Kosloskey
        Participant

          How about routing to an intermediate localhost thread set and applying an alert to either of those threads?

          You could also try Field level routing if a it is a component issue.

          Or perhaps a TrxID proc to coorrect the issue.

          Of course the real fix may belong with the source system.

          Just curious how is the Message/Event Type malformed?

          email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

        • March 20, 2015 at 11:30 am #82256
          Brandon Grudt
          Participant

            You could also create a tcl script that looks for “goobered” values in MSH-8 and sends an email when that happens or create a TrxID proc to fix it in the engine.  I’m with Jim, though.  Any manipulation in Cloverleaf is more of a band-aid if you are getting garbage from the sending system.

          • March 24, 2015 at 7:07 pm #82257
            Mark Brown
            Participant

              I agree that fixing it at the source would be the best solution, but that doesn’t seem to be happening.

              I think I’ll go with the option of the intermediate local host thread. That seems to be least amount of headache.

              Thanks for all your replies.

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