Recover_33 and message loss

[Keith McLeod]

When I bounce a thread that is performing resends after the timeout period has been reached, I notice that the message that is being resent appears to be lost and that the next message in queue starts in on the resend process.  How can I prevent the loss of messages?  I am using a later version Recv33_38.tcl or modification of recover_33.tcl.  The resend part seems to work great, but I am concerned about the loss of messages. Any advice…..

Topic

[Michael Hertel]

Check use “recovery database” on the inbound source thread.

Make sure retries is set to -1 on the outbound thread.

[Russ Ross]

The recover_33 procs are several different TPS procs designed to work together.

It took me a while to figure out just how to get these procs to work together properly and many people have had similar struggles with them until they have a working example.

I’ve attached my homegrown document ( Resend.doc ) I created many years ago describing how to configure NetConfig to use the recover_33 procs effectively.

Over the years this has been one of my most popular documents.

Even though the procs have evolved over the years and many places have a personalized copy of the recover_33 procs, the configuration is still simliar today.

If your problem is due to a mis-configuration issue then my attahced resend.doc might help you identify your issue.

If your problem is the result of using a more evolved recover_33 proc then this document will be much less helpfull.

Good luck and let us know how it goes.

Russ Ross
RussRoss318@gmail.com

[Charlie Bursell]

Really weird Russ, but then again  😀

[Author]

Replies