error database message state 402 send ok tcl proc failure

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf error database message state 402 send ok tcl proc failure

  • Creator
    Topic
  • #47987
    William Grow
    Participant

      Hi,

       Just curious about something.  Messages kept getting stuck in the error database for an outbound thread in which the the send_ok proc was set, the tps_inbound_reply proc was set, but the reply_gen proc wasn’t set. I checked with a coworker and his thoughts was that the timeout was being exceeded but since there wasn’t a reply_gen proc to either resend or kill the message_handle for the outbound message, that this caused the engine to stick all subsequent messages into the error database in state 402. Can anyone comment?

    Viewing 1 reply thread
    • Author
      Replies
      • #57237
        Charlie Bursell
        Participant

          He is correct.  The recover_33 procs work as 3 procs together.

          The sendOK proc expects the global to be empty when it gets a new message.  If not, that indicates the previous message was not handled and you are haeded for serious memory leaks.

          Why would you have a timeout and then do nothing?

        • #57238
          William Grow
          Participant

            Charlie,

             Thanks for replying.  This was a mistake someone here in the office made when setting up the outbound thread.

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