Can I change the ADS configured normalRetryTime from a ClientAPI?

Craig.Tait

We have an interactive provider service which relies on sending a CLOSED_RECOVER when service is intermittently unavailable.  This appears on our EMA client as follows:

[pool-2-thread-1] INFO <company.pkg>.EmaClient - Status Message for null: (-): StatusMsg
    streamId="5"
    domain="System Domain"
    state="Open / Suspect / None / 'F9: Server has gone down. Will recall when a server becomes available.'"
    itemGroup="00 03"
    name="AR9TO"
    serviceId="10002"
    serviceName="<SERVCIENAME>"
StatusMsgEnd

The subscription is automatically retried after 120 seconds (basis the normalRetryTime configured on the ADS), but we would prefer a shorter retry time for our client.  Can this timeout be configured within EmaConfig.xml or must we change the setting on the ADS?  Can the ADS setting be varied on a per-channel or per-provider basis?

Jirapongse

@Craig.Tait

Thank you for reaching out to us.

Typically, the items will be recovered by ADH or ADS so you need to change the settings on ADH or ADS.

!++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
!
! *ads*"${svc}"normalRetryTime : 120
!#help
!    normalRetryTime: { 1 - N seconds }
!
!    If an item cannot be obtained from any available server, either on
!    the initial request, after a server failure, or upon a closed recoverable
!    status from the provider, for clients with single open enabled, the ADS
!    will attempt to re-open the item after this amount of time (in seconds)
!    has elapsed.
!
!    Default value: 120 seconds
!#end
!++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

According to the description, this configuration is per service. However, please contact the RTDS support team directly via LSEG Support to verify it.