Randomly not receiving ACK’s

[Darrell Glover]

I have a client that has a VPN connection from the hospital to a vendor.  Randomly we will not receive an ACK back from the vendor, so messages just start queuing up.   I assume if I disable “Await Replies” it will prevent the issue, but I really don’t want to do that.  Is there a better way to handle the issue?  Right now, we have the Inbound replies Timeout set to -1 and we are having to monitor the queue depth for the thread.  When the queue starts to build, we have to restart the thread to get it going again.  We are opening at ticket with the vendor, but historically they are not very good at resolving these sorts of issues.

Topic

[Jerry Sawa]

I handle that issue with an “and” alert.

I see if thread has

• Connection is “up” for over 5 minutes
• and O/B Queue depth >=1 for over 5 minutes
• and Last Receive is >= 300 seconds (5 minutes)

If all those are true, I prestart the thread.   Resolves the issue 99% of the time.

[Jerry Sawa]

Attached document is kind of old, I’ve modified some settings to match what I have in my previous post.

Attachments:

You must be logged in to view attached files.

[Darrell Glover]

Thank you, Jerry!  Unfortunately, this client has migrated to the Cloverleaf Cloud which appears to have very limited functionality for Alerts, so I don’t think it is an option.  However, I will be using your recommendations for another client for a similar issue (they are not on the cloud).

[Author]

Replies