Subject: Antwort: Questions Regarding the Intialization Process of a Master Agent

From: "Frank Fock" <[email-masked]>
Date: Tue, 16 Jan 2001 14:38:25 +0100

Hi Nurit,

The registration process is always triggered by the subagents.
Thus, the master must not store the registration table in non
volatile memory, because it cannot restore the connections to
subagents.

So, upon starting up the master agent just waits until a subagent
registers. Consequently, when a master agents reinitializes the
related subagents should be reinitialized too. This can be done
by a process manager (i.e., a script controlling the master /
subagent processes) or by simply restarting/reinitializing a
subagent when its connection to the master is broken.

Regarding persistency of transactions, IMHO there is no
persistency, because a transaction that hangs will time out
and will then always be terminated by the master agent.
(Hopefully before the manager times out its SNMP
request!)

Hope this helps.

Best regards,
Frank

Nurit Sprecher <[email-masked]>
15.01.01 11:35

        An:     "[email-masked]'" <[email-masked]>
        Kopie:  (Blindkopie: Frank Fock/MAIN/MC1)
        Thema:  Questions Regarding the Intialization Process of a Master Agent

Hi all,
I have some questions regarding the AgentX protocol. It will be great if
someone may make it clear to me.

There are some uncertainty (for me) regarding the recovery process of a
master agent. What is the initialization process of a starting up master
agent?
Apparently, the registration table can be kept in a non-volatile memory,
and
upon starting up; the master agent may restore the table.  Is that the
situation? Or may be it is expected to re-perform the registration
process?
Personally, I think that the later case is unreasonable.

In such a case, the question is how the master agent handles a case where
the master agent failed in a middle of a transaction? Is there a
requirement
for persistency of a transaction managed by the master agent?

Thanks in advance, Nurit.

(See attached file: att1.htm)