Queries regarding Indications behaviour.

Hi ,

                We have some queries related to the functionality of indications in Open Pegasus. It would be great if someone can confirm on these behaviors.


1.       Cimserver shutdown fails with pending Indication delivery - Indications were subscribed. Indication listener was shut down. Stop the cimserver. Cimserver does not shut down.


2.       Out of order indication delivery - Indication subscription was created for ClassA followed by indication subscription to ClassB. Two life cycle indications were generated(IndicationA for instance Class A followed by IndicationB for instance of Class B).  IndicationB(indication  for class B) was delivered followed by delivery of IndicationA (indication for class A). The expected behavior is IndicationA delivered first and then IndicationB. We suspect that indication thread created for indicationB finding the subscription  earlier in the list when compared to subscription for class A causing it to deliver the indication out of order.


Regards
Karthik