changeset: 4577:07e88841d268
branch: opensaf-4.2.x
parent: 4574:b424e8c4e643
user: Hans Feldt <hans.fe...@ericsson.com>
date: Tue Oct 29 21:57:47 2013 +0100
summary: amf: change saAmfResponse to be synchronous in TerminateCallback
context [#570]
changeset: 4578:19f8ca3ee0e3
branch: opensaf-4.3.x
parent: 4575:03c46e565f76
user: Hans Feldt <hans.fe...@ericsson.com>
date: Tue Oct 29 21:57:47 2013 +0100
summary: amf: change saAmfResponse to be synchronous in TerminateCallback
context [#570]
changeset: 4579:b26e27059891
tag: tip
parent: 4576:5a7622688312
user: Hans Feldt <hans.fe...@ericsson.com>
date: Wed Oct 30 06:55:31 2013 +0100
summary: amf: change saAmfResponse to be synchronous in TerminateCallback
context [#570]
---
** [tickets:#570] AMF: ava down event ignored in TERMINATING state**
**Status:** fixed
**Created:** Wed Sep 18, 2013 06:45 AM UTC by Hans Feldt
**Last Updated:** Wed Oct 16, 2013 07:51 AM UTC
**Owner:** nobody
If a component crash or exit in context of the terminate callback, AMF will not
use the "ava down" event to trigger cleanup and finish component termination.
Instead the CallbackTimeout is awaited which can be very long.
This is a problem if this happens during an upgrade, it will cause the upgrade
to fail potentially leading to system restore.
Ignoring the event (in avnd_err.c) was added in:
changeset: 1646:92e6e65eefc0
user: Nagendra Kumar <nku...@emerson.com>
date: Thu Aug 26 18:43:31 2010 +0530
summary: Ticket 1433: Allowing dynamic configuration changes for AMF
logical entities
reasons unclear. This has to be revisited. As far as I can tell there is no
"race" between the ava down event and the response message. Normally a process
calls saAmfResponse(OK) and then exit(0). saAmfResponse(OK) under the hood
sends a message and at least TIPC will do "run to completion" meaning it will
post it to the receivers (amfnd) socket receive buffer. After that the process
exit and a topology event is created and written to another socket receive
buffer (MDS lib for amfnd). Eventually the MDS thread in amfnd context will
receiver both messages and write them to amfnd mailbox with the same prio.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
