Dequeue messages

This topic has 4 replies, 3 voices, and was last updated 10 years, 10 months ago by bill bearden.

Creator

Topic
November 26, 2013 at 5:09 pm #53935

Bryon Kury
Participant

Is there a cloverleaf method for de-queuing messages.

If a “NAK” is being sent and resent, i want to move it out of the way so i can get other messages to process. I would like to de-queue the message and move on. we are currently doing that with TCL code.
Creator

Topic

Viewing 3 reply threads

Author

Replies
- November 26, 2013 at 6:20 pm #79599
  
  James Cobane
  Participant
  
  If you don’t care whether the reply is an ACK or NAK, you could simply put the ‘hcitpsmsgkill’ proc in the TPS Inbound Reply context and that will simply KILL every reply message and the engine will simply send the next message upon receipt of the ACK/NAK.
  
  Jim Cobane
  
  Henry Ford Health
- November 26, 2013 at 6:25 pm #79600
  
  Bryon Kury
  Participant
  
  No, i would not want to kill the message. i just need to get it out of the way for the messages behind it to process.
- November 26, 2013 at 7:28 pm #79601
  
  James Cobane
  Participant
  
  My post was referencing KILLing the actual ACK/NAK, not the outbound message.
- November 26, 2013 at 10:46 pm #79602
  
  bill bearden
  Participant
  
  Bryon,
  
  Kinda guessing here…
  
  In NetConfig for that thread, what is the setting of Retries on the Outbound tab in the Outbound Data section? Is it set to -1?
  
  On some of our connections, messages error out after a few retries. That isn’t exactly what you are asking for (they aren’t KILLed). But, at least, the thread doesn’t stop processing other messages. Maybe you can put something in Send Fail Procs.
  
  Bill
Author

Replies

Viewing 3 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.