#1375 Amf: need to wait for both terminate cbk response and application exit during application restart

[Nagendra Kumar]

Refer ticket #1326.

During application restart, once Amf receives terminate callback response from application, Amf tries to instantiate the application again using CLC-CLI command. There is some chance that application might have sent the terminate callback response, but is taking time before it exits/terminates actually. And if this is the case, then Amf will be trying to instantiate the application, which is yet to get terminated or which is still instantiated.

There could be some handling required for such situations in application's CLC-CLI script as done for middleware components in #1326. But, if Amf could wait for application to get terminated after receiving the terminate callback response, the specific changes in the CLC-CLI script is not required.

But some of the obvious things need to be discussed:
1. How much Amf can wait for receiving application down event after receiving terminate callback?
2. If there could be some timeout to wait, what actions should be taken if the application down is not received during that time-period.

[Anders Widell]

First of all, I think this is not specific to component restart; it should always be done when terminating a component.

Instead of just waiting for the response to the terminate callback, AMF should wait for both the response and for avadown. The time-out is given by saAmfCompTerminateCallbackTimeout. Both of these events need to happen before the timeout. Otherwise the cleanup script is called.

[Nagendra Kumar]

The fix will take care of 'Sa-Aware preinstantiable' and 'proxied preinstantiable'.

[Nagendra Kumar]

changeset: 6622:826a29978d3f
tag: tip
user: Nagendra Kumarnagendra.k@oracle.com
date: Thu Jun 18 15:11:31 2015 +0530
summary: amfnd: wait for applcation exit during its termimation [#1375]

[staging:826a29]