handling missing acks on Inbound threads

This topic has 1 reply, 2 voices, and was last updated 18 years, 4 months ago by Robert Kersemakers.

Creator

Topic
August 10, 2006 at 7:22 pm #48696
Nancy McDaniel
Participant
I have an interface that I have configured to require acks when receiving data. It is an inbound interface, I have a 30 second timeout. When I check my status on the inbound thread, the msg in and the msg out counts do not match. What are others doing to monitor this and make sure that no data gets lost.

Do I need to put the ownership on the sending system and not be as concerned about the making sure that I don’t lose data from the sending system?

thanks,

nancy
Creator

Topic

Viewing 0 reply threads

Author

Replies
- August 11, 2006 at 1:42 pm #59423
  Robert Kersemakers
  Participant
  Hi Nancy,
  
  I’m not sure about the concept of requiring an ACK on an inbound thread. Usually the inbound thread will receive a message and then reply with an ACK to the sending system. It’s up to the sending system to resend the message if no ACK is received within a specified time (time-out) or if a NACK is received. (Maybe that is what you meant…)
  
  It is true though that the msg in and msg out counts will differ most of the time. They should be equal, but as soon as messages are resend because of a time-out or NACK, the counts will differ.
  
  I’m not actively monitoring this, because the sending system should make sure that the message is received correctly. In case of a time-out or a NACK, the sending system should resend the message of alert someone that a message has failed.
  
  So after testing the interface, only the errors should be monitored and resolved.
  
  Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands
Author

Replies

Viewing 0 reply threads

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