Please note, i shall be pushing this patch Today. Timeout!
This patch was floated after the discussion below:
https://sourceforge.net/p/opensaf/mailman/opensaf-devel/thread/patchbomb.1391418319%40opensaf-VirtualBox/#msg31923614
Alternatively the standby process just logs some message at start. That should
do the trick too
If you go the other path please keep saflog as it is and add an additional init
function
Skickat från min Sony Xperia™-smartphone
---- Mathivanan Naickan Palanivelu skrev ----
Well there is an option 4(not sure if we are talking about the same, i.e. your
option 2) that can work well within the framework of 4.2 and 4.3 systems.
Option 4): Split saflog() into safloginit() and saflogwrite() i.e. move the
synchronous calls loginitialize, streamopen to safloginit() and safloginit()
has to be done much early in the lifecycle of the LOG user/client. i.e. CLM,
NTF, AMF both ACTIVE and STANDBY instances.
This can indeed be additionally done, in the context of this ticket. Will take
a stab at that.
Having said that, if we discuss the theory part
a) i don't think increasing the csisetcallback will in reality create any
functional problem for the clients of CLM or NTF because, the mode of service
provided to these clients are asynchronous in nature i.e. such
subscribers(clients) are not held up on a blocking call! And as such, for
runtime changes, saflog is attempted by these serviceproviders(CLM, NTF) only
after doing their core job, i.e. servicing their subscribers(like sending
subscription/track callbacks) first and then they try to update the IMM and/or
send notifications and/or log it to saflog.
b) A client's HA timeout should indeed be greater than the system defined
timeout value of an API(say, the blocking variants). In the worst caes
scenarios, there is a realistic chance for the serviceconsumer getting a
TIMEOUT when requesting a service(API). However, upon timeout if this client
retries later, the call would indeed succeed.
Cheers,
Mathi.
---
** [tickets:#720] Increase csisetcallback timeout value for services using LOG
API(eg:- CLM, NTF) **
**Status:** review
**Labels:** csisetcallbacktimeout MDS api timeout 10 seconds
**Created:** Wed Jan 15, 2014 10:14 AM UTC by Mathi Naickan
**Last Updated:** Thu Jan 30, 2014 10:17 AM UTC
**Owner:** Mathi Naickan
It has been observed (in pre 4.4) on field that a client of LOG (in the
specific case - CLM, but in general all LOG API users) can get blocked when
calling saflog() or LOG() because the LGS was busy doing a file operation.
The current MDS API timeout is 10 seconds and the csisetcallback timeout for
all(except SMF has about 30 seconds) services is 10 seconds.
Now, in the worst case scenario, the saflog() internal utility can take 30
seconds before returning.
This ticket proposes that the csisetcallbacktimeout is increased to 40 seconds
for users of LOG in 4.2 and 4.3.
---
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.
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
