- **status**: assigned --> review
---
** [tickets:#3314] imm: Deadlock between pbe and ccb applied on a pbe object**
**Status:** review
**Milestone:** 5.22.04
**Created:** Mon May 02, 2022 03:20 PM UTC by Hieu Hong Hoang
**Last Updated:** Mon May 02, 2022 03:20 PM UTC
**Owner:** Hieu Hong Hoang
Generally, a critical ccb won't be processed if the pbe doesn't start and we
can't set implementer to an object if exists an active ccb which applies on
that object. In this issue, an active ccb applied on an pbe object and was in
critical state while pbe wasn't start. The system failed to start pbe because
that ccb is active and the ccb wasn't be processed because the pbe wasn't
start. It is a deadlock here.
Log analysis:
* pbe failed to start:
~~~
<143>1 2022-05-02T14:57:51.553529+02:00 SC-1 osafimmnd 389 osafimmnd [meta
sequenceId="58624"] 389:imm/immnd/ImmModel.cc:15066 TR TRY_AGAIN: ccb 4 is
active on object 'opensafImm=opensafImm,safApp=safImmService' bound to OI name
'OpenSafImmPBE'. Can not set re-attach implementer
2022-05-02 14:57:51.554 SC-1 osafimmpbed: ER saImmOiImplementerSet for
OpenSafImmPBE failed 6
~~~
* ccb was blocked in critical state
~~~
2022-05-02 14:57:52.534 SC-1 osafimmnd[389]: WA Timeout (6) on transaction in
critical state! ccb:4
2022-05-02 14:57:52.534 SC-1 osafimmnd[389]: WA There are ccbs blocked in
critical state, waiting for pbe process to re-attach as OI
~~~
---
Sent from sourceforge.net because [email protected] 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
