Lost Message

Chuck,

If the message is in SMAT, the engine was able to successfully transmit the message (but not necessarily have it process in the receiving system).  Did the receiving system acknowledge it?  I suspect that the receiving system did not process it even though it was sent.  Depending on the data contained in the acknowledgements received from ConnectR, you should be able to tie the acknowledgement received to the message that was sent.  If the message was acknowledged, then you can look to the vendor to figure out why they didn’t process.

Hope this helps.

Jim Cobane

Henry Ford Health

Chuck,

You are waiting forever for a reply.

So if the receiving system never sends one you don’t get a chance to resend.

The check-ack proc only gets involved once you receive an ack as you have things configured.

How are you configured under Timeout Handling?  I beleive you either need to use the recover procs or set up your timeout handling to resend OB message.  If these aren’t configured, then you can milk the queue by bouncing the thread and losing each message basically.  You can test this using the tcp testing tool and not responding to the messages you send to it.

Chuck,

Well you need to set your Timeout to something other than -1. The value -1 means wait forever which means you will never time out thus never resend the message.

To determine what should go in there, try collaborating with the receiving system to get a feel for the maximum amount of time it might take for an acknowledgment to be sent. After all you don’t want to do too many resends only as an exception.

Note that value may need to be adjusted with testing.

Also note that if there is a firewall or VPN involved you could get into a situation where the receiving system will appear to never respond and thus you could do a lot of resends before you detect that.