recover_33

[Keith McLeod]

When using the recover_33 procs, where is the best place to establish a counter for messages resent? Typically this counter should stay at its initialized value until it actually resends messages. I am guessing that a global variable be used.  I would think that a place to reinitialize would be in the killObSave proc since this is used when an ACK is recieved. I would want to increment the counter in the resendObSave.  I would be using the counter info in a resend alert proc to inform an analyst that an ACK is not being received by this thread.  I have code that works except if I bounce the thread with messages in queue during a resend. This tells me that the initial location should not be in killObSave… I am sure that someone has this down to a science.  Let me know….

Topic

[Russ Ross]

Keith McLeod:

I’m interested in being able to have a notification triggered when the same message has been resent so many times and noticed you had a post asking for input on this.

I was wondering what you came up with or any input on the matter you might have.

I’ve begun brainstorming with my co-worker (Jim Kosloskey) about this and will be writing something myself if necessary to fire an alert if a message is resent a specified number of times.

Jim and I did discuss modifying the existing recover_33 procs to include such logic like you talked about.

However, I feel better writing something that is not married to recover_33 so directly.

Perhaps I will write a tps_resend_alert_count_reset proc that I stack with the tps_save_ob_msg proc in the Send OK Procs stack.

Then I might have a tps_resend_alert_count_check proc that I stack with the tps_resend_ob_msg proc in the Reply Generation stack.

Charlie Bursell:

I recall you have a post asking how to enhance the alerts and I think being able to fire an alert based on how many times the same message gets resent is worthwile.

My motivation for needing such an alert is that it is more proactive way to alert because once you have say 10 resends on the same message you know you are headed for trouble and there is no need to wait for other less proactive alerts to notify you much later than necessary.

FYI –  my arguments for the proc might be something like this

Code:

{RESEND_ALERT_COUNTS_LIST {10 100 1000 10000}}
{RESEND_ALERT_EMAIL       {page_hub_on_call,page_ods_on_call,email_hub_team}}

which means email notices would be sent out up to a maximum of 4 times in this case when

resend_count = 10

resend_count = 100

resend_count = 1000

resend_count = 10000

Russ Ross
RussRoss318@gmail.com

[Charlie Bursell]

I have done this many times at many sites Russ.  Not brain surgery  🙂

If you do not want to mess with resend procs then it is simple enough to write a simple proc which goes in front.  Simply look at the MSH.10 (I think that is correct) for the Message ID.  Save it off in a global, or more preferable, in a namespace variable.  Do the same with a count.  If the account exceeds your desire, send the mail.  I use tclMail but you can use what you want.

As for doing it in alerts you will be able to do that using the Tcl defined alert in 5.7.

[Author]

Replies