There is a reason why this ticket has not been implemented.
The SaImmOiTimeout attribute is *one* single valued config attribute
in the *single* config object defined by SAF for the IMM service.
Thus any update done to the value of this config attribute would impact
*all* operations on *all* OIs.
It should be obvious but I will say it anyway: this could be dangerous.
The current hard code value of 6 seconds works for nearly all OIs.
It is long enough to give ample time for an OI to do its validation
in completed, which is likely to be the most sensitive callback.
Syncronous admin operations have an explicit timeout per call and
so should not be a problem.
If this is implemented, then the value should never be set lower than
the derfault 6 seconds and not as high as the default timeout of 10 seconds.
THus valid nond default values would be limited to:
7, 8 or 9 seconds.
Is it worth it ?
In addition, since this enhancement has apparently been prioritized up
to be incuded in 4.4, I assume that there is some application that has
problems, or anticipates it will have problems, with the current default.
I think that application should descibe why it thinks it would need a
timeout longer than 6 seconds. I think it is more likely that they have
missunderstood something or that they are doing something wrong than
that they actually legitimately need this. IF the information is proprietary
then it could be sent via direct email to me and not in the ticket.
I suppose I am arguing that this ticket should have been removed,
or that if needed, then it should be a timeout associated with each
implementer-name.
---
** [tickets:#16] IMM: Support the saImmOiTimeout config attribute in the
SaImmMngt class**
**Status:** unassigned
**Created:** Tue May 07, 2013 08:28 AM UTC by Anders Bjornerstedt
**Last Updated:** Mon Sep 16, 2013 10:51 AM UTC
**Owner:** Anders Bjornerstedt
There is a need for configurable timeout for IMMND OI upcalls, i.e.
the timeout for how long the imm-service will wait for a reply on
an OI upcall. Currently there is a hardwired timer of 6 seconds.
Version A.03.01 of the SAF IMM standard does in fact define such
an attribute 'saImmOiTimeout', which is one reason that A.03.01 is
actually not backwards compatible with A.02.01 (schema upgrades
are not supported in A.03.01).
Actually the 'saImmOiTimeout' is already present in the definition
of the SaImmMngt? class used by the OpenSAF IMM in 4.1. This despite
that the OpenSAF IMM does not support the A.03.01 version.
But the imm service ignores this attribute currently.
This enhancement proposes that the imm service shall respect the
setting of this attribute.
This enhancement is related to the more general issue of providing
an OI for the imm service itself.
http://devel.opensaf.org/ticket/503
Migrated from:
http://devel.opensaf.org/ticket/2021
---
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.------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
