Clovertech

UPoC Thread Routing Issue

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › UPoC Thread Routing Issue

  • Creator
    Topic
  • June 6, 2014 at 3:58 pm #54252
    Todd Hamilton
    Participant

      I would like to create a single process with three Threads.

      Thread A. Protocol: tcpip server. Receives HL7 message from external system. Static raw route message to Thread B

      Thread B. Protocol: UPoC. Perform complex transformation of message using TCL code. Static raw route message to Thread C

      Thread C. Protocol: tcpip Client. Sends HL7 message to external system

      I can’t get the above to work the way I want. I think the issue is with Thread #2.

      When I create a create a single process with only TWO Threads.

      Thread A. Protocol: tcpip server. Receives HL7 message from external system A. Static raw route message to Thread C

      Thread C. Protocol: tcpip Client. Sends HL7 message to external system

      It works.

      Can you provide insight on areas I can look at in order to troubleshoot?

      todd.hamilton.omaha@gmail.com
      (402) 660-2787

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • June 6, 2014 at 5:20 pm #80730
        Todd Hamilton
        Participant

          When I turned on EO enable_all, the log file produces an ever growing list of repeating lines (below)

          When Checking msg [0.0.2], owner ‘EpicAdtFltr’, state 11

          [dbi :log :INFO/3: a_xlate:06/06/2014 11:51:42] Message not selected

          The file is ever growing with the above lines. That may be my problem. What do the two lines above mean?

          todd.hamilton.omaha@gmail.com
          (402) 660-2787

        • June 6, 2014 at 6:12 pm #80731
          James Cobane
          Participant

            Todd,

            Just curious as to why you want to route to thread B and not directly to C? With all three threads in the same process, you’re not shifting any of the processing as all the work will be done in the same process.  You could simply perform the tcl transformation in a pre-route proc to thread C.  

            Jim Cobane

            Henry Ford Health

          • June 9, 2014 at 1:38 pm #80732
            Todd Hamilton
            Participant

              Good point.  What I am really looking for is a successful example of a thread that gets messages routed to it using Message Routing; processes the message using a TPS; and routes the message to another thread using Message routing.  

              I am new to Cloverleaf and working on some initial/foundation approaches to out architecture.  I seem to be missing something in the middle thread.  I think it has something to do with my misuse of disposition (CONTINUE/OVER) and or misplacement of the TPS.

              todd.hamilton.omaha@gmail.com
              (402) 660-2787

            • June 13, 2014 at 7:14 pm #80733
              Todd Hamilton
              Participant

                This issue is resolved.  My problem was that I was not using correct code for the OVER on the TPS.

                todd.hamilton.omaha@gmail.com
                (402) 660-2787

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