The problem here is when a ccb has been aborted (for ANY reason) then
the imm always
returns ONE and the same error code: SA_AIS_ERR_FAILED_OPERATION.
This is crucially important because it must be crystal clear to the
om-client if the CCB was aborted or not.
Any subtle different *reasons* for why the CCB was aborted are conveyrd
through the error strings.
/AndersBj
Nagendra Kumar wrote:
> Thanks Anders.
> Can imm return NO_RESOURCES(the same return type returned by OI) to smfd and
> smfd, if it gets NO_RESOURCES, it retry(if it could be implemented).
>
> -Nagu
>
>
> ---
>
> ** [tickets:#750] AMF: creating multiple CSIs are rejected**
>
> **Status:** accepted
> **Milestone:** future
> **Created:** Mon Jan 27, 2014 10:24 AM UTC by Hans Feldt
> **Last Updated:** Tue Mar 18, 2014 10:03 AM UTC
> **Owner:** Nagendra Kumar
>
> AMF supports adding one CSI per CCB to an unlocked SI. This means if several
> CSIs are to be added, many CCBs will be performed by SMF (from a campaign).
> However since the first CSI create is still "pending" when the second CSI one
> comes to AMF, the second one is can be rejected (by AMF). All depending in
> timing.
>
> One problem is that the OI completed callback does not give the OI any chance
> to say TRYAGAIN. It is either accept or reject.
>
> Adding a delay to the campaign between each CSI create is not a plausible
> solution thus AMF needs to support this case.
>
>
> ---
>
> Sent from sourceforge.net because you indicated interest in
> <https://sourceforge.net/p/opensaf/tickets/750/>
>
> To unsubscribe from further messages, please visit
> <https://sourceforge.net/auth/subscriptions/>
>
---
** [tickets:#750] AMF: creating multiple CSIs are rejected**
**Status:** accepted
**Milestone:** future
**Created:** Mon Jan 27, 2014 10:24 AM UTC by Hans Feldt
**Last Updated:** Tue Mar 25, 2014 01:34 PM UTC
**Owner:** Nagendra Kumar
AMF supports adding one CSI per CCB to an unlocked SI. This means if several
CSIs are to be added, many CCBs will be performed by SMF (from a campaign).
However since the first CSI create is still "pending" when the second CSI one
comes to AMF, the second one is can be rejected (by AMF). All depending in
timing.
One problem is that the OI completed callback does not give the OI any chance
to say TRYAGAIN. It is either accept or reject.
Adding a delay to the campaign between each CSI create is not a plausible
solution thus AMF needs to support this case.
---
Sent from sourceforge.net because [email protected] is
subscribed to http://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
http://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
