- **status**: invalid --> unassigned
- **Comment**:
This issue is observed, if ErrorReport or ErrorCLear api is called from a stand
alone AMF executable, rather than a part of AMF component.
So, to reproduce the issue :
1 )Call the saAmfInitialize.
2) Call the saAmfFinalize with the handle obtained in first step.
3) Call the ErrorReport api with the finalize handle.
Proper return value is obtained if the ErrorReport api is called as part of
component which is spawned by AMF and saAmfRegister is mandatory to be invoked
as part of initialization.
---
** [tickets:#248] "amf: Incorrect return code from saAmfComponentErrorReport_4
() and saAmfComponentErrorClear_4()". **
**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Thu May 16, 2013 06:41 AM UTC by Praveen
**Last Updated:** Mon Nov 07, 2016 05:41 AM UTC
**Owner:** Nagendra Kumar
Migrated from http://devel.opensaf.org/ticket/2817.
Changeset:3728
When saAmfComponentErrorReport_4() and saAmfComponentErrorReport_4() are
called after finalizing the amfHandle(calling saAmfFinalize()), both of them
returns SA_AIS_ERR_VERSION instead of SA_AIS_ERR_BAD_HANDLE.
---
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.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
