I think the correct approach would be to introduce a new topology event to fill the blind area between real instance creation via CC and member spawned event. So, as soon as CC receives a instance start up call, CC would add the member to topology and will send a new event with a new state possibly.
On Tue, Oct 28, 2014 at 10:06 AM, Chamila De Alwis <chami...@wso2.com> wrote: > > Hi Raj, > > > On Tue, Oct 28, 2014 at 2:23 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> CC will add it to the topology, send member created event and send member >> terminated soon after that. Now AS will get this event and remove the >> member from its lists. We can't send member terminated events for members >> which are not in the topology. If we do so, these events will be rejected >> by message processors. > > > Is it logically correct to send a member created event for a member that > is obsolete? Can't we allow a new path to complete termination sequence for > an obsolete member? > > > Regards, > Chamila de Alwis > Software Engineer | WSO2 | +94772207163 > Blog: code.chamiladealwis.com > > > -- Best Regards, Nirmal Nirmal Fernando. PPMC Member & Committer of Apache Stratos, Senior Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/
