On 02/24/2014 02:00 PM, William R Elliott wrote: > A couple more questions > > Our processes are multithreaded and one thread is responsible for the > interaction with the AMF. That thread responds > within the configured time limit with the saAmfResponse to the receipt of > terminate. The process main thread > continues to run to be able to do a clean stop (completes the current unit of > work). Does OpenSAF expect the > process to be stopped after responding to the terminate?
So your component is sa-aware. The important thing here is that AMF will give the active assignment to another component after the CSI Set quiesced callback. So your component cannot hold on to any shared resource after the CSI set callback. If so you have split brain on component level. Just to clarify... Thanks, Hans ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
