[tickets] [opensaf:tickets] #2230 pyosaf: imm om and oi utils bindings don't handle BAD HANDLE
--- ** [tickets:#2230] pyosaf: imm om and oi utils bindings don't handle BAD HANDLE ** **Status:** unassigned **Milestone:** 5.0.2 **Created:** Sun Dec 18, 2016 01:21 PM UTC by Johan Mårtensson **Last Updated:** Sun Dec 18, 2016 01:21 PM UTC **Owner:** nobody The utils functions for imm om and oi add retry loops that shield the user from writing repetitive retries for each call to handle TRY AGAIN. The retry loop doesn't handle BAD HANDLE which means that the user will still need to wrap each call to check for BAD HANDLE and re-initialize the handle if required. This should be done automatically in the retry loop. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2230 pyosaf: imm om and oi utils bindings don't handle BAD HANDLE
- **status**: unassigned --> accepted - **assigned_to**: Hieu Nguyen - **Blocker**: --> False - **Milestone**: future --> 5.17.10 - **Comment**: In progress --- ** [tickets:#2230] pyosaf: imm om and oi utils bindings don't handle BAD HANDLE ** **Status:** accepted **Milestone:** 5.17.10 **Created:** Sun Dec 18, 2016 01:21 PM UTC by Johan Mårtensson **Last Updated:** Sun Dec 18, 2016 01:21 PM UTC **Owner:** Hieu Nguyen The utils functions for imm om and oi add retry loops that shield the user from writing repetitive retries for each call to handle TRY AGAIN. The retry loop doesn't handle BAD HANDLE which means that the user will still need to wrap each call to check for BAD HANDLE and re-initialize the handle if required. This should be done automatically in the retry loop. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2230 pyosaf: imm om and oi utils bindings don't handle BAD HANDLE
Hi, According to Johan's idea: "This should be done automatically in the retry loop". I want make clearly about this: In BAD\_HANDLE case difference with TRY\_AGAIN case + TRY\_AGAIN is a simple case that's mean try to call current function agian. + BAD\_HANDLE have many complex cases. Example for a CCB: * Init OM handle => OK * Init Admin Owner handle => OK * Init CCB handle => OK * Create a object => OK * Modify this object => OK * Apply CCB => BAD_HANDLE If we handle BAD\_HANDLE case use Johan's idea, we need keep track all data and all steps of CBB in above case, NOT only re-intialize. That takes many effort to store data and process complex. I think user who know clear their steps. When TRY\_AGAIN error occurred, they can easy rollback their steps. Regards, --- ** [tickets:#2230] pyosaf: imm om and oi utils bindings don't handle BAD HANDLE ** **Status:** accepted **Milestone:** 5.17.10 **Created:** Sun Dec 18, 2016 01:21 PM UTC by Johan Mårtensson **Last Updated:** Tue Oct 03, 2017 09:11 AM UTC **Owner:** Hieu Nguyen The utils functions for imm om and oi add retry loops that shield the user from writing repetitive retries for each call to handle TRY AGAIN. The retry loop doesn't handle BAD HANDLE which means that the user will still need to wrap each call to check for BAD HANDLE and re-initialize the handle if required. This should be done automatically in the retry loop. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2230 pyosaf: imm om and oi utils bindings don't handle BAD HANDLE
- **status**: accepted --> wontfix - **Comment**: I set this ticket to "wontfix". If you have any comments, let me know ? --- ** [tickets:#2230] pyosaf: imm om and oi utils bindings don't handle BAD HANDLE ** **Status:** wontfix **Milestone:** 5.17.10 **Created:** Sun Dec 18, 2016 01:21 PM UTC by Johan Mårtensson **Last Updated:** Wed Oct 04, 2017 03:51 AM UTC **Owner:** Hieu Nguyen The utils functions for imm om and oi add retry loops that shield the user from writing repetitive retries for each call to handle TRY AGAIN. The retry loop doesn't handle BAD HANDLE which means that the user will still need to wrap each call to check for BAD HANDLE and re-initialize the handle if required. This should be done automatically in the retry loop. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2230 pyosaf: imm om and oi utils bindings don't handle BAD HANDLE
Another ticket #2602 related to support handle ERR_BAD_HANDLE case. It's propose support more error codes should be handled as well, NOT only ERR_BAD_HANDLE. It's not "This should be done automatically in the retry loop". Please contact who handle this ticket get more detail. https://sourceforge.net/p/opensaf/tickets/2602/ --- ** [tickets:#2230] pyosaf: imm om and oi utils bindings don't handle BAD HANDLE ** **Status:** wontfix **Milestone:** 5.17.10 **Created:** Sun Dec 18, 2016 01:21 PM UTC by Johan Mårtensson **Last Updated:** Wed Oct 04, 2017 03:52 AM UTC **Owner:** Hieu Nguyen The utils functions for imm om and oi add retry loops that shield the user from writing repetitive retries for each call to handle TRY AGAIN. The retry loop doesn't handle BAD HANDLE which means that the user will still need to wrap each call to check for BAD HANDLE and re-initialize the handle if required. This should be done automatically in the retry loop. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
