- **status**: accepted --> invalid
- **Comment**:
During a saImmOiRtObjectX() call, we cannot accept a new admin op as the OI
handle cannot be used concurrently. So adding a thread will not solve this
situation. Adding a dedicated IMM thread will help in some respsect, to ensure
amfd can handle admin ops if it is busy performing other work (that is not
using the OI handle).
---
** [tickets:#1928] amfd: admin ops return with SA_AIS_ERR_TIMEOUT**
**Status:** invalid
**Milestone:** 5.2.FC
**Created:** Fri Jul 22, 2016 06:12 AM UTC by Gary Lee
**Last Updated:** Tue Nov 22, 2016 03:40 AM UTC
**Owner:** Gary Lee
Sometimes IMM can take a long time when AMFD updates persistent runtime
attributes. During this period, if an admin op is issued towards AMFD, AMFD
will not be able to respond and the admin op results in TIMEOUT. Furthermore,
IMM marks AMFD's OI handle as BAD.
2016-07-04 17:39:50 SC-1 osafimmnd[436]: WA ERR_BAD_HANDLE: Client 120259215631
not found in server
We probably need to create a thread in AMFD whose job is to update runtime
attributes.
---
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
