The is also a timeout on the OI callback (the create callback harboring the
Augmentation).
Normally the OI timeout is shorter than the IMMA_SYNCR_TIMEOUT and so normally
the
OM client should get an error on the ccb-create downcall before timeout.
But if the OM lcient has erduced the syncr timeout or the OI has increased its
OI timeout then you could end up getting ERR_TIMEOUT on the OI side. This
without anything being
wrong anywhere.
---
** [tickets:#1503] IMM: Augumented CCb client went down the OM client should
get err**
**Status:** assigned
**Milestone:** 4.5.2
**Created:** Fri Sep 25, 2015 09:18 AM UTC by Neelakanta Reddy
**Last Updated:** Fri Sep 25, 2015 09:18 AM UTC
**Owner:** Neelakanta Reddy
OM on node1 and OI on node2.
OM creates an object.
In OI augument by creating an object and the OI client goes down.
The CCb get aborted in IMM database.But the OM create API will not get return
value and after SYNC_TIMEOUT OM API receives TIME_OUT.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
