- **Component**: imm --> unknown
---
** [tickets:#2889] imm: avoid BAD_HANDLE result on requests after timeout on
CCB apply**
**Status:** fixed
**Milestone:** 5.18.09
**Created:** Wed Jul 04, 2018 07:58 AM UTC by Vu Minh Nguyen
**Last Updated:** Thu Aug 30, 2018 12:45 PM UTC
**Owner:** nobody
**Attachments:**
-
[ccb_apply_get_TIMEOUT_result_in_BAD_HANDLE.txt](https://sourceforge.net/p/opensaf/tickets/2889/attachment/ccb_apply_get_TIMEOUT_result_in_BAD_HANDLE.txt)
(30.3 kB; text/plain)
If CCB apply (IMMND_EVT_A2ND_CCB_APPLY) gets TIMEOUT (e.g: PBE is hung during
that time), here is what will be happening at IMMND and IMMA:
IMMND purges that synchronous request by doing following main jobs:
1) Attemp to abort CCB even the CCB state is in critical.
2) Remove client node from client dabase.
At IMMA, inside `saImmOmCcbApply()` call, `imma_proc_recover_ccb_result()` is
invoked to get CCB result by sending `IMMND_EVT_A2ND_RECOVER_CCB_OUTCOME` to
the IMMND. After the CCB is commited, `imma_proc_recover_ccb_result()` returns
SA_AIS_OK to `saImmOmCcbApply()` and then SA_AIS_OK to user.
Later on, when user performs any IMM call on that IMM OM handle such as
`saImmOmFinalize()` will result in `BAD_HANDLE` as the client node has already
removed in #2 above.
See syslog and imma trace from the attachment.
---
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
