Clovertech

Inbound thread not sending messages.

› Clovertech Forums › Cloverleaf › Inbound thread not sending messages.

  • Creator
    Topic
  • April 22, 2021 at 3:37 pm #118782
    Joe Baranski
    Participant

      Aside from this being on a problematic site (had 2 panics today alone), we’re having peculiar problems with an inbound ADT thread that is showing/writing message but not sending the messages.  The same messages will process perfectly if I simply resend them from the smatdb, not making any changes.  At first I thought it may have been related to using a newer TCPIP protocol with new cl OK/ACK procs in 19.1, or any other tclprocs or the XLate written for that outbound thread.  But even after stripping it down to the bare bones, no route procs or XLates, switching back to old OK/ACK procs, and rebuilding the outbound thread from scratch it’s still not sending messages.  I triple checked the NetConfig and everything looks clean.

      Has anyone else encountered this?  Are there background job or configs which may be causing this?

       

      Thanks in advance!

    • Creator
      Topic
    Viewing 2 reply threads
    • Author
      Replies
      • April 22, 2021 at 6:56 pm #118783
        Jim Kosloskey
        Participant

          Just for clarification, are there ANY Outbound threads receiving messages just not this one?

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

        • April 22, 2021 at 11:02 pm #118784
          Charlie Bursell
          Participant

            Check to make sure it is not something simple like having Outbound Only checked on the inbound thread.

            Turn the EO up and see if you can trace the messages through the engine.

            Are the messages still in either the recovery or error database?

          • April 23, 2021 at 8:27 am #118785
            Joe Baranski
            Participant

              Thanks for the responses, turns out the problem was much deeper than that.  The Monitor Daemon was stuck from the last panic.  Had to end up going in to command line and ps -ef | grep for anything tied to that site and kill it from there.

               

              Thanks for the quick responses

          • Author
            Replies
          Viewing 2 reply threads
          • You must be logged in to reply to this topic.