- **status**: review --> fixed
- **Comment**:
default(4.5):
changeset: 5487:b6dfd46ec94e
user: Zoran Milinkovic <zoran.milinko...@ericsson.com>
date: Fri Jul 25 15:00:42 2014 +0200
summary: imm: add support for configurable OI callback timeout [#16]
changeset: 5488:b00e638de216
user: Zoran Milinkovic <zoran.milinko...@ericsson.com>
date: Fri Jul 25 15:01:27 2014 +0200
summary: imm: use IMMA_OI_CALLBACK_TIMEOUT for setting OI callback timeout
[#16]
changeset: 5489:52dbf65847a0
user: Zoran Milinkovic <zoran.milinko...@ericsson.com>
date: Fri Jul 25 15:02:16 2014 +0200
summary: immtests: add test cases for OI callback timeout [#16]
changeset: 5490:e6ab06fa6808
tag: tip
user: Anders Bjornerstedt <anders.bjornerst...@ericsson.com>
date: Thu May 08 18:10:17 2014 +0200
summary: imm: update immsv/README for IMMA_OI_CALLBACK_TIMEOUT [#16]
---
** [tickets:#16] IMM: Configigurable OI callback server-side timeout per
OI-handle.**
**Status:** fixed
**Milestone:** 4.5.FC
**Created:** Tue May 07, 2013 08:28 AM UTC by Anders Bjornerstedt
**Last Updated:** Thu Jul 17, 2014 03:08 PM UTC
**Owner:** Zoran Milinkovic
There is a need for configurable timeout for IMMND OI callbacks,
i.e. the timeout for how long the imm-service will wait for a reply on
an OI callback. 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 the official A.03.01 standard. Schema upgrades
are however supported by the OpenSAF IMM).
The 'saImmOiTimeout' is already present in the definition
of the SaImmMngt class since OpenSAF 4.1. This despite
that the OpenSAF IMM does not support the A.03.01 version.
The imm service ignores this attribute currently.
But the concept of having *one* config attribute controlling the timeout
for *all* OIs in the system, has severe problems. See comments below.
Because of this, we alter the proposed solution to the problem.
Instead of using this single config attribute, we will use an environment
variable recognized by the IMMA library. This will follow the same pattern
as the existing IMMA_SYNCR_TIMEOUT that configures the timeout for
blocking downcalls (in both the OM and OI libraries).
A new environment variable IMMA_OI_CALLBACK_TIMEOUT will be recognized by
the OI library. Just as for the existing IMMA_SYNCR_TIMEOUT, this environment
variable is sampled by the SaImmOiInitialize function for initializing an
oi-handle. The handle will have that timeout associated with it for the rest
of its lifetime. Different OI handles can have different timeouts by changing
the value of IMMA_OI_CALLBACK_TIMEOUT prior to each saImmOiIntitialize.
The library will send the handles callback timeout-value down to the server
as an added part to the message used by saImmOiImplementerSet
Migrated from:
http://devel.opensaf.org/ticket/2021
---
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.
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
