Re: Queries regarding Indications behaviour.

For question 2  I think you can look the defect   9013(Indications arrives
out-of-order from provider to handler. ) which is part of already  released
2.12  version  which seems to address  the issue

      Regards
      Ashok


                                                                           
             "Karunanithy,                                                 
             Karthik"                                                      
             <KarthikPachaiapp                                          To 
             an.Karunanithy@ne         "[email protected]"         
             tapp.com>                 <[email protected]>         
                                                                        cc 
             07-11-2012 16:40          "Subbaiah, Kamalalochana"           
                                       <[email protected]> 
                                                                   Subject 
                                       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