21
●2 ●6 ●10
This is Redhat Linux Enterprise 6 running C++ RFA-based(rfa8.0.1.L1.linux.rrg) interactive provider. Is there a way via config to set RFA requestTimeout?
Apologies for any misunderstanding. My original question is regarding "requestTimeOut parameter for request side/consumer". Where can one set this parameter on the client side, or, if possible in either rmdstestclient, or ADS, or ADH?
@Kam.Anjorin
Thank you for your participation in the forum. Are any of the replies below satisfactory in resolving your query? If yes please click the 'Accept' text next to the reply that best answers your question. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question.
Thanks,
-AHS
Hi,
Thank you for your participation in the forum.
Are any of the replies below satisfactory in resolving your query?
If yes please click the 'Accept' text next to the most appropriate reply.
Otherwise, you may share an answer and then accept it. This will guide all community members who have a similar question.
Thanks,
AHS
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
AHS
7.6k
●15 ●6 ●9
For RFA consumer application, you can set the requestTimeout in RFA configuration file. You need to add the following config to the Connection section.
\Connections\<Connection Name>\requestTimeout = <New Value>
The default value for RFA C++/.NET is 45000 which is 45 sec. Please find more details about RFA configuration from RFA Configuration file which provided under folder "<RFA Package>/Docs"
If you need to set in in other APIs, please check the configuration in API configuration guide. The rmdstestclient is part of infra tools and I'm not sure that it can set the requestTimeout like the TREP APIs or not.
7.6k
●15 ●6 ●9
We do not have requestTimeout for provider interactive.
As far as I understand the requestTimeOut parameter is for request side/consumer, it's time the connection waits for before resending the request.
Not sure why you need requestTimeout parameter on Provider side?
