Clovertech

Delete on recycle

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Delete on recycle

  • Creator
    Topic
  • October 13, 2011 at 12:53 pm #52749
    Paul Von
    Participant

      I have an interface that when it has a connection problem it has a queue that increases over time.  This is working as expected.

      The problem is when the thread is stopped and restarted all the messages in the queue are deleted.  The interface is configured to store ack messages and there are no ACKs.

      Multiple setting have been tried but the issue has not been resolved.

      Any ideas??

      Current setting:

      Thread Tab

      Protocol: pdl-tcpip

      Checked – Save inbound messages

      – thread_name_ack

      Checked – Save outbound messages

      – thread_name_out

      Properties button

      PDL – mlp_tcp.pdl

      Outbound Tab

      Retries: -1

      Interval: 10

      Send OK Procs: save_ob_msg

      Checked – Await Replies

      Timeout Handling Button

      Reply Generation

      Procs – resend_ob_msg

    • Creator
      Topic
    Viewing 4 reply threads
    • Author
      Replies
      • October 13, 2011 at 4:38 pm #75371
        Jim Kosloskey
        Participant

          Paul,

          In your Thread Tab do you have ‘Use Recovery database’ checked (I suspect not).

          If not check it and try again.

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

        • October 13, 2011 at 4:50 pm #75372
          Paul Von
          Participant

            Jim,

            I checked the “Use Recovery Database” then stopped and started the process twice.

            Good suggestion, but the problem still exists.

          • October 13, 2011 at 9:23 pm #75373
            Paul Bishop
            Participant

              I have found that if any of the threads in a string of threads do not have the “Use Recovery Database” marked, then it will delete the recovery messages in the last thread when cycled.  for example:

              Threads A, B, and C have the box unmarked.  Thread D has it marked

              A routes to B.  B is a local TCP connection to C.  C routes to D which sends it to a vendor via TCP.  D hangs up and has messages queued.  You cycle it and all the messages are removed from the recovery database.  When A, B, and C have the box marked, then the messages don’t get removed when D is cycled.

              Paul Bishop
              Carle Foundation Hospital
              Urbana, IL

            • October 14, 2011 at 12:28 pm #75374
              Paul Von
              Participant

                Paul,

                Thank you for providing the answer.  When I first checked use “Use Recovery Database” on all the outbound interfaces it did not resolve the problem.

                When I also checked “Use Recovery Database” on the inbound interface the problem was resolved.

                All the threads both inbound and outbound need to have the “Use Recovery Database” checked

                Thank you

              • October 14, 2011 at 12:43 pm #75375
                Russ Ross
                Participant

                  Recovery database is applicable to the thread receiving the inbound messages and routes them, which threw me off in the beginning, too.

                  That means the thread routing the message to the outbound interface(s) needs to have the recovery database turned on and in most cases is not applicable to the outbound interface.

                  Almost all the threads where Jim Kosloskey and I work are configured outbound only with no recovery database and we don’t have message loss when any interfaces are recycled on Cloverleaf 5.3rev2 and before running on AIX.

                  However, all the threads not configured as outbound only that receive messages and route them to other threads, do have recovery datase turned on in production.

                  However, if we overlook turning on the recovery data base on the receiving thread that routes to any outbound thread(s) then queued messages go away especially if the inbound listener on Cloverleaf is recycled.

                  I did not pay close enough attention to see if the messages go away when the outbound interface is recycled in the case when recovery database is turned off on the inbound thread.

                  I didn’t think they went away until the inbound thread was recycled.

                  So if you aren’t also recyling the receiving thread with the routes on it and are seeing the messages dissappear I will conceed to your observations until I do simialr test myself someday.

                  Russ Ross
                  RussRoss318@gmail.com

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