Do we see the problem even when access control is NOT enabled ?
---
** [tickets:#995] IMM: after immnd restart amfd fails to become class
implementer**
**Status:** assigned
**Milestone:** 4.5.0
**Created:** Tue Aug 19, 2014 10:36 AM UTC by Hans Feldt
**Last Updated:** Tue Aug 19, 2014 10:36 AM UTC
**Owner:** nobody
Seems like the IMM access control changes triggers some new behavior around the
IMM "resurrect" logic that cause client failure after immnd restart.
Test case is simply to kill immnd on a controller. In most cases it ends up
with node reboot since amfd cannot become class implementer. Timeout is
returned which is not handled properly.
If this cannot be resolved rather quickly I am afraid the IMM access control
feature should be backed out.
---
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
