That is why I tried to restrict the number of retries. Handling bad handle is different to me between OI and OM.
I think what you did in #517 is great. But it only covers a subset of the places where IMM reads occur. I don't see a feasible way of fixing this fully with threads with the restricted time and amount of code changes we can make for 5.0? On 19 May 2016 7:57 PM, Nagendra Kumar <[email protected]> wrote: Hi Gary,                Yes, but this will make Amfnd to hang and will get created the same problem as mentioned in #517. Please check Amfd handling the BAD_HANDLE in a separate thread and the tickets Ander W has mentioned.  Thanks -Nagu  From: Gary Lee [mailto:[email protected]] Sent: 19 May 2016 15:21 To: Nagendra Kumar Cc: [email protected]; [email protected]; [email protected]; [email protected] Subject: RE: [PATCH 1 of 1] amfnd: add preliminary support for BAD OM handles [#1833]  Hi Nagu I think we definitely should for the next release, but what about 5.0? Gary ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
