Hi All, We are using OpenSAF 5.2, and are seeing cases where we get the error code: SA_AIS_ERR_TIMEOUT. According to the spec, An implementation-dependent timeout occurred before the call could complete. It is unspecified whether the call succeeded or whether it did not.
>From a design viewpoint, what are we supposed to do when something "might have >succeeded"? Are there any practical recommendations or suggestions on how to >handle this condition? In our particular case, we are trying to do a node LOCK_INSTANTIATE operation. There are 2 scenarios to consider: 1. If I assume the LOCK_I Failed, I can send the command again. However, if the command actually succeeded, then sending the command again will result in an illegal state transition. How do I determine if it succeeded or failed? 2. Is there any type of hierarchical association of the notifications? For example, if issuing the node LOCK_I command were to generate 100 notifications, can I assume that as long as I see the ADMINISTRATIVE_STATE_CHANGE_NOTIFICATION, that reports the node is LOCK_I, I can disregard the other 99 notifications (SERVICE_INSTANCE_UNASSIGNED, etc). In other words, does the receipt of the highest level notification imply that all the other lower ones have occurred? Thanks. Jim ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
