Alerts — Opening state and last recevied

[David Coffey]

I have an interface where there is not a persistent connection, is the last received timer reset every time the connection is terminated?

Topic

[Bob Richardson]

Greetings,

We are running Integrator 5.8.6.0 on AIX 6.1 TL7SP4 Virtualized.

For years I have been at Cloverleaf R & D to fix the Last Received and Last Sent alerts to reset when a thread has been cycled (stop/started).

From our experience these alerts will fire falsely after the thread is restarted or just started then “settle down” and fire per the configuration.

Apparently the monitor program (daemon) measures the last or sent

times in its MSI (shared memory) for the thread and now that it is running will test the condition and can fire.

If other shops have a different experience we would be interested to hear from you.  Or if you discovered (stumbled into?) a workaround.

Hope this helps.

[Russ Ross]

The trick we use to reset alerts once fired is to have a cron job touch the default.alrt file once an hour.

This way the alert will go off once an hour until the problem is resolved.

This has been a good trade off for us so we get reminded but not too often.

Russ Ross
RussRoss318@gmail.com

[David Coffey]

Based on the responses I don’t think I made myself clear.  However the owner of the sending system finally agreed to alter their timeout parameters and now the issue no longer exists.

[Author]

Replies