Clovertech

2 different threads pointing to the same 3rd thread

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › 2 different threads pointing to the same 3rd thread

  • Creator
    Topic
  • December 8, 2008 at 9:42 pm #50501
    John Zalesak
    Participant

      I am about to set up a situation where I will have two different threads in the same site, but different processes, point to a third thread in a third process in the same site.

      One thread carries maybe 2,000 msg per day.  The second thread will carry maybe 5 messages per day.  I have carved out this second low volume thread to handle messages that need to be delayed a few minutes before sending them on.  I did not want to put a busy thread to sleep.

      Do I have to worry about the two threads trying to send to the same third thread at the same time or will the protocol handle this properly???

    • Creator
      Topic
    Viewing 6 reply threads
    • Author
      Replies
      • December 9, 2008 at 8:36 am #66335
        garry r fisher
        Participant

          Hi John,

          The messages should simply join the inbound queue and get processed unless there is more to your setup than you have described.

          Regards

          Garry

        • December 9, 2008 at 7:04 pm #66336
          Anonymous
          Participant

            I have many threads sites and processes. Sending from multiple threads to a single thread works very well in the same process or another process.

          • December 11, 2008 at 7:42 am #66337
            Robert Kersemakers
            Participant

              Just as an afterthought: inter-process communication (routing messages from one thread to another thread of another process) is considered as something to be avoided. It is much better to send messages to another process (or site) by way of tcp/ip.

              Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

            • December 11, 2008 at 2:01 pm #66338
              Jim Kosloskey
              Participant

                We tend to stay away from cross process communication ourselves.

                We also tend to discourage situations where a single outbound receives its input from two different inbounds – even not using cross process communication.

                We encourage the receiving system to set up and additional connection for the new type of data.

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

              • December 11, 2008 at 3:01 pm #66339
                Gary Atkinson
                Participant

                  I just had situation where the vendor needed several different types of data ADT, ORM, ORU, DFT, RDE and wanted it all on one port.  I created a different site to avoid cross process communication.  I also found this a much “cleaner” approach.

                • December 12, 2008 at 3:20 pm #66340
                  Hongle Sun
                  Participant

                    Hello, Jim. What could be the side effect you can think of situations where a single outbound receives its input from two different inbounds, can you explain more in details? Thanks

                  • December 12, 2008 at 11:27 pm #66341
                    Steve Pringle
                    Participant

                      Yes, I’m also very interested in the reasons for the following:

                      “We tend to stay away from cross process communication ourselves.

                      We also tend to discourage situations where a single outbound receives its input from two different inbounds – even not using cross process communication.”

                      thanks,

                      Steve

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