Sending REPLYs.

[Robert Denny]

We have a results in interface from a DI device.

On it we receive MICRO and DI lab results, along with SSU messages.

On the 1st of June we had a incident that occurred for just a few seconds. During that time we first received 3 copies of the same message and the system moved on and sent 3 copies of the next message in the sequence.

then we started receiving 7 copies of the same message for about 20 results.

then it settled down and started functioning normally. We are only using the TCL proc replygen and we were not archiving Outbound messages nor were we awaiting replies.

Could this have been an issue with Cloverleaf that caused the issue. The LAB folks are thinking Cloverleaf did not send an ACK back. There were no messages in the Error database nor were there errors in the process logs.

Topic

[Russ Ross]

I had a one off event this reminds me of from a vendor interface that was configured to resend every second if an ACK was not received from cloverleaf.

It took their sending interface 10 seconds to connect once started so each time it was started or cycled I had 10 messages of the same thing already queued up when it connected.

Check to see how long the vendor waits for an ACK before resending the same message.

I typically don’t go any shorter than 30 seconds and then keep increasing until my resend problems settle down.

Russ Ross
RussRoss318@gmail.com

[Author]

Replies