case MfFieldTypes.ALPHANUMERIC :
case MfFieldTypes.LONG_ALPHANUMERIC :
nestedFieldList.add(EmaFactory.createFieldEntry().ascii(fid, field_value ));
break;

Values at RIC for Display Name :

DSPLY_NAME "l

DSPLY_NAME " 4

I am using EMA Java latest version (3.9.2.0)

I am implementing an RTO WebSocket implementation, and from what I encountered and read, you cannot download the dictionary from the WebSocket version of the RTO.

Given this fact, I am using the FileDictionary to make the EMA load it from local files.

The problem I have is that the dictionary files are inside a jar. The only solution that works seems to be to read the file and copy it into a temporary file and use that temporary file's path and give it to the EMA library to load it from there.

Is there any other way to load a dictionary file that is inside a jar besides that?

Thank you

if both ADS endpoints configured in the failover channel list are unavailable (i.e., a total outage), the application should stop instead of staying in EMA’s native retry loop.

Before implementing a custom logic, I would like to better understand the expected behavior of EMA in this scenario and check if a recommended approach already exists.

Our understanding is that:

-EMA internally manages all failover and retry behavior
-the retry loop continues indefinitely if no ADS endpoints are reachable
-this is the expected default behavior when using ChannelSet and reconnect parameters in the EmaConfig

However, our client requires that the application:

-terminates when all ADS endpoints fail
-returns a specific exit code/writes an identifying log entry
-optionally allows this via a configuration property (e.g. onTotalOutage.mode = retry | stop)

Questions:

• Which callbacks or state events are most appropriate to detect a “total outage”?
  For example:

ChannelDown
ChannelDownReconnecting
ConnectionLost
lack of available channels in the Reactor/Consumer

• Is there an officially recommended way to interpret these events?
  
• Is there any supported configuration or API feature to disable retry?
  Or should this requirement always be implemented at application level, by intercepting EMA events and explicitly shutting down the consumer?
  
  
• Is there any known best practice for applications that must exit on loss of all ADS endpoints?
  We would like to follow the most aligned solution from an EMA perspective.

Before proceeding, we would appreciate guidance or confirmation on how EMA is expected to handle this case.

Any insights or suggestions would be greatly appreciated.
Thanks in advance to the EMA team and the community!

Ale

Is the WSB feature mandatory for using <ChannelType value="ChannelType::RSSL_ENCRYPTED"/> and <EnableSessionManagement value="1"/>?

I extracted the items above by referring to the 470 tutorial. When I don’t use the WSB feature, no segmentation fault is triggered—this is based on the 113 tutorial.

My app's simplified entrance code show below. Could you please point out my problems?

ps:

I find that SIGINT is used by EMA framework itself, so I use SIGTERM for elegant exit for my own app.

Technically, may I know the meaning of the following StatusMsg?

The RIC was subscribed previously successfully and getting the updates continuously for hours, then got this message, after re-subscribed the RIC, the updates recovered.

StatusMsg

streamId="3901"

domain="MarketPrice Domain"

state="Closed / Suspect / Not entitled / 'Reverify '"

name="AMZN.NB"

nameType="1"

serviceId="257"

serviceName="ELEKTRON_DD"

StatusMsgEnd

In our test, we repeatedly stopped and restarted our application 6 times in a row. After the restarts, a heap inspection shows multiple DataDictionaryImpl instances still present in memory. It looks like these objects are not being cleaned up when the consumer is shut down.

For reference:

API: EMA Java

Version: 3.9.1.1

JVM: OpenJDK Runtime Environment (Red_Hat-17.0.18.0.8-1) (build 17.0.18+8-LTS)

The shutdown code simply calls:

OmmConsumer.uninitialize();

Based on the API documentation, I expected this to fully tear down the consumer and release associated resources, including dictionary-related objects.

However, after multiple restart cycles in the same JVM, I can see multiple DataDictionaryImpl objects remaining in memory.

My questions:

Is OmmConsumer#uninitialize() expected to fully clean up dictionary objects such as DataDictionaryImpl?

Is there an additional shutdown step required to completely tear down the EMA API?

Could this be related to dictionary loading/caching behaviour inside EMA?

Any guidance would be appreciated.

us-east-1-aws-1-med.ppe.int.optimized-pricing-api.refinitiv.com
Service ID: GE-Hxxxxx

• RTSDK(by using C#)
• Websocket

The question is
1) if we decided to use RTSDK CSharp or Websoket then we need build our own Real time optimizer end points in our infrastructure?
2) Please guide us what protocol will be used if we build the application by using RTSDK lib?

3) In the both the method do we need to get the token first from (api.refintiv.com ) and by using that token we need to login into RTO end points

We have developed a software that publishes market data to a TREP system: first an initial Refresh Message, and then Update Messages which contain only the fields that have changed (bid/ask/mid prices and timestamp).

However, on the target system, the item seems to contain dozens of fields that we have set neither in the Refresh nor in the Updates. These fields have invalid values like special characters.

As the invalid fields mess up the client's UI display, we bypass the issue by sending only Refresh Messages - but this is not a long-term solution.

When we connect a simple test consumer (taken from the RTSDK) with the target TREP system (i.e. we consume the market data we are publishing ourselves), the first RefreshMsg we receive contains the additional invalid fields; all further Refreshes contain only the fields we explicitly set in the message (→ see attached log file).

My question is: where do these unwanted fields come from? Can there be an issue on our side - e.g. something with our EmaConfig or the dictionary?

Thank you in advance!

Helmut

Is there a way to get what comes out of the socket which I assume would be much lighter. We're looking at a way to get at the raw data before the framework enriches it with the metadata. The metadata is static in enumtype.def we can add it ourselves when we need it?

Thank you

We are using the same user login concurrently from two different servers. The application configuration is identical on both servers.

On one server, subscriptions work as expected.

On the other server, we consistently receive Access Denied / Not entitled status messages for a specific subset of RICs when we attempt to subscribe to them.

The affected RICs are:

AUCASH=
AUCASH=RBAA
AUDFIX10H=WM
AUDNZD=S
AUD=S
AUUS3BSRBS=WPAC
MONEY
NZCASH=RBNZ
NZDFIX14H=WM
NZD=S

A typical status message looks like:

State: Closed / Suspect / Not entitled
Text: "Access Denied: User req to IDN for Prod e.g. - WWRIVXMKT"
Service: hEDD
Domain: MarketPrice

What makes this confusing is that these exact same RICs subscribe successfully on the other server at the same time using the same login.

So far, we’re considering a few possibilities, but haven’t been able to confirm any of them:

Are there RIC-level entitlements that restrict concurrent usage of the same login from multiple hosts?

Do any of the above RICs have stricter entitlement or concurrency rules than standard instruments?

Is it even possible for entitlements to behave differently depending on the server, host, or connection context?

If anyone has seen similar behaviour with the EMA API or can point out something obvious we might be missing that would be great.

Thanks!

We are connecting to HMDS WebSockets using the EMA library and are creating the config dynamically. During the creation, we have 1 primary region and 2 back up regions, which are translated to a channel for each region.

The issue we have is that when a disconnect happens, the library will automatically switch to the next channel, which meant that it will switch to the back up region after 1 disconnect on primary. Back up regions do not work as well, so a disconnect will usually happen quite quickly on the back up channels, until it reaches the primary region again and which will work well after that.

Is there a way in which we could specify the reconnect strategy to the library? For example, after a disconnect happens it should retry connecting to the primary 3 times and only if all 3 times it fails should it try the back up channels. And if it reconnects successfully to the primary region, if another disconnect occurs, it will retry again 3 times the primary and so on.

Thanks

  while (field_list.forth()) {

    const auto &entry = field_list.getEntry();

    int16_t fid = static_cast<int16_t>(entry.getFieldId());
    if (entry.getCode() == refinitiv::ema::access::Data::BlankEnum) {

      continue;

    }

    try {

      switch (entry.getLoadType()) {

      case refinitiv::ema::access::DataType::RealEnum: {

        const auto &real_value = entry.getReal();

        data.double_fields[fid] = real_value.getAsDouble();

        break;

      }

      case refinitiv::ema::access::DataType::IntEnum: {

        data.int64_fields[fid] = static_cast<int64_t>(entry.getInt());

        break;

      }

      case refinitiv::ema::access::DataType::UIntEnum: {

        data.int64_fields[fid] = static_cast<int64_t>(entry.getUInt());

        break;

      }

…

I wanted to understand what how is trdprc_1 cleared at closing - do we get null or 0 from exchanges?

We used OmmConsumer to get the data by onUpdateMsg callback function.

The issue happens when the period is during auction close or PM market close.

There is around 30k+ number to update during that period.

You can see the screendump of log that callback of onUpdateMsg is stopped at 16:08:12.

But it is resumed at 16:08:29. There is 27 seconds of delay.

It happens regularly everyday. We also checked that the RTDS server side has no such delayed record.

Could you provide some advice for the coding and troubleshooting?

I am currently using C# to get market data and wondering whether the data is being conflated from the server (3 update per second?)

Below is snippet of my LSEG.Ema.Access.RequestMsg

        private static RequestMsg CreateEquityRequestMsg(InstrumentSymbol instrumentSymbol)

        {

            var fieldArray = new OmmArray();

            fieldArray.AddInt(6);     // LAST_PRICE

            fieldArray.AddInt(22);    // BID

            fieldArray.AddInt(30);    // BID_SIZE

            fieldArray.AddInt(25);    // ASK

            fieldArray.AddInt(31);    // ASK_SIZE

            fieldArray.AddInt(3372);    // OFF_CLOSE vs 21 HST_CLOSE

            fieldArray.AddInt(3855);  // QUOTIM_MS

            fieldArray.Complete();


            var payload = new ElementList()

                .AddUInt(EmaRdm.ENAME_VIEW_TYPE, 1)

                .AddArray(EmaRdm.ENAME_VIEW_DATA, fieldArray)

                .Complete();


            var request = new RequestMsg()

                .ServiceName("ELEKTRON_DD")

                .Name(instrumentSymbol.Ric)

                .Payload(payload)

                .InterestAfterRefresh(true);


            return request;

        }

If it's not conflated, can you please show me how to configure it?

Thank you.

I've written an NI provider application using RTC. Now I'm trying to login on a pre-production RTDS system.

I'm getting the following two logger messages which seem to indicate that the connection is established correctly, but login fails ("non-consumer attempting login"):

loggerMsg
    TimeStamp: 10:29:22.803
    ClientName: ChannelCallbackClient
    Severity: Success
    Text:    Received ChannelUp event on channel smds006@HZAE_via_jmp01
	Instance Name Provider_1_1
	Connected component version: ads3.8.1.L1.linux.rrg 64-bit
loggerMsgEnd

loggerMsg
    TimeStamp: 10:29:22.886
    ClientName: LoginCallbackClient
    Severity: Error
    Text:    RDMLogin stream was closed with status message
	username 
	usernameType 1
	position <not set>
	appId <not set>
	applicationName <not set>
	singleOpen 1
	allowSuspect 1
	optimizedPauseResume 0
	permissionExpressions 1
	permissionProfile 1
	supportBatchRequest 0
	supportEnhancedSymbolList 0
	supportPost 0
	supportRtt 0
	supportViewRequest 0
	
	State: Closed / Suspect / Usage error / 'Login rejected. Non-consumer attempting login.'
loggerMsgEnd

I developed the app using EMA. The OmmProvider instance is created using an adjusted EmaConfig.xml andOmmNiProviderConfig().applicationId(APPLICATION_ID).username(USER). As mentioned before, I used RTC during development, and never had any connection issues there.

I also tried to set up a consumer connection to the same channel, using the same app ID and username. This seems to succeed - I get a similar "ChannelUp" message as above, followed by a status "Closed/F10: Not In Cache", which is expected.

This looks like a configuration issue to me, either on my side or on the remote side. I would be grateful for any hint regarding the steps that are necessary to fix it.

Thank you in advance,

Helmut

On Saturday morning, a number of our subscriptions received status messages indicating Closed / Suspect / Not Entitled / Reverify. These messages were delivered via onStatusMsg. Based on this, our application logic interpreted the state as DOWN.

However, shortly afterwards we continued to receive data for the same subscriptions via onUpdateMsg(UpdateMsg, OmmConsumerEvent). As a result, the application transitioned back to UP (our assumption being that if updates are flowing, the application is effectively up).

This has raised a few questions about the correct handling strategy:

Should we resubscribe to the affected symbols when receiving these status messages?

Should we log off and re-establish the session?

Or should onStatusMsg be treated as advisory, with application health primarily determined by the presence or absence of updates?

Any guidance on the intention of these status messages and recommended handling would be great.

If there is an alternative solution to achieve this, please do let us know. Requesting your assistance at the earliest as the VPN will be discontinued by end of the year.

In the below, we have requested for Fid 101, but we got all the Fids in return. I can see

"RSSL_SC_UNSUPPORTED_VIEW_TYPE", how to rectify this?

<!-- rwfMajorVer="14" rwfMinorVer="1" --><requestMsg domainType="RSSL_DMT_SYSTEM" streamId="5" containerType="RSSL_DT_ELEMENT_LIST" flags="0x44C (RSSL_RQMF_STREAMING|RSSL_RQMF_MSG_KEY_IN_UPDATES|RSSL_RQMF_HAS_QOS|RSSL_RQMF_HAS_VIEW)" qosDynamic="0" qosRate="1" qosTimeliness="1" dataSize="36">
<key flags="0x3 (RSSL_MKF_HAS_SERVICE_ID|RSSL_MKF_HAS_NAME)" serviceId="10000" name="HTS4H"/>
<dataBody>
<elementList flags="0x8 (RSSL_ELF_HAS_STANDARD_DATA)">
<elementEntry name=":ViewType" dataType="RSSL_DT_UINT" data="1"/>
<elementEntry name=":ViewData" dataType="RSSL_DT_ARRAY">
<array itemLength="2" primitiveType="RSSL_DT_INT">
<arrayEntry data="101"/>
</array>
</elementEntry>
</elementList>
</dataBody>
</requestMsg><!-- rwfMajorVer="14" rwfMinorVer="1" --><refreshMsg domainType="RSSL_DMT_SYSTEM" streamId="5" containerType="RSSL_DT_FIELD_LIST" flags="0xE8 (RSSL_RFMF_HAS_MSG_KEY|RSSL_RFMF_SOLICITED|RSSL_RFMF_REFRESH_COMPLETE|RSSL_RFMF_HAS_QOS)" groupId="1" qosDynamic="0" qosRate="1" qosTimeliness="1" dataState="RSSL_DATA_OK" streamState="RSSL_STREAM_OPEN" code="RSSL_SC_UNSUPPORTED_VIEW_TYPE" text="*Refresh Completed" dataSize="97">
<key flags="0x3 (RSSL_MKF_HAS_SERVICE_ID|RSSL_MKF_HAS_NAME)" serviceId="10000" name="HTS4H"/>
<dataBody>
<fieldList flags="0x8 (RSSL_FLF_HAS_STANDARD_DATA)">
<fieldEntry fieldId="101" dataType="RSSL_DT_ASCII_STRING" data="USD"/>
<fieldEntry fieldId="301" dataType="RSSL_DT_REAL" data="0.00"/>
<fieldEntry fieldId="302" dataType="RSSL_DT_REAL" data="0.00"/>
<fieldEntry fieldId="303" dataType="RSSL_DT_REAL" data="0.00"/>
<fieldEntry fieldId="304" dataType="RSSL_DT_REAL" data="0.00"/>
<fieldEntry fieldId="305" dataType="RSSL_DT_REAL" data="0.00"/>
<fieldEntry fieldId="306" dataType="RSSL_DT_REAL" data="0.00"/>
<fieldEntry fieldId="307" dataType="RSSL_DT_REAL" data="0.00"/>
<fieldEntry fieldId="310" dataType="RSSL_DT_REAL" data="0.00"/>
<fieldEntry fieldId="312" dataType="RSSL_DT_REAL" data="0.00"/>
<fieldEntry fieldId="401" dataType="RSSL_DT_REAL" data="0.00"/>
<fieldEntry fieldId="411" dataType="RSSL_DT_ASCII_STRING" data="USD=0.00,100.00"/>
<fieldEntry fieldId="501" dataType="RSSL_DT_REAL" data="0.00"/>
<fieldEntry fieldId="503" dataType="RSSL_DT_REAL" data="0.00"/>
<fieldEntry fieldId="504" dataType="RSSL_DT_REAL" data="0.00"/>
<fieldEntry fieldId="507" dataType="RSSL_DT_REAL" data="0.00"/>
</fieldList>
</dataBody>
</refreshMsg>

＜照会事項＞
以下の日時、RICにてEMA経由でデータ取得を行ったところ、
2025/4/24 10:30（日本時間）では取得不可、2025/4/24 13:00（日本時間）は取得可でした。
2025/4/24 10:30 にRIC：DIBJP1WD=　について、情報取得できなかった理由をご教示願います。

　・取得不可のRIC　：　“DIBJP1WD=”
　・取得不可の日時 ：　2025/4/24 10:30
　　※上記RICは、2025/4/24 13:00 に取得した際は取得できております。

＜補足＞
以下の通り、RIC、FID(393,3,875,1010)を指定し、EMA経由でデータを取得しております。
DIBJP1MD=,393,3,875,1010
DIBJP1WD=,393,3,875,1010

また、2025/4/24 10:30の取得不可事象は、RIC：DIBJP1WD= のみ取得不可、他のRIC(DIBJP1MD= 等)は取得可となっております。

I'm trying to write unit tests that test writing to and reading from FieldList containers. However, on the first reading access on populated containers, I'm getting a Segmentation Fault. The reason is that functions like "reset()" or "forth()" are de-referencing FieldList::_pDecoder, and this member seems not to be initialized.

Example:

void MyTest()
{
	FieldList fieldList;
	fieldList.addReal(22, 3990, OmmReal::ExponentNeg2Enum);
	fieldList.complete();
	while (fieldList.forth())  // <== SEGFAULT (FieldList::_pDecoder == NULL)
	{
		// ... check field entries ...
	}
}

What am I doing wrong? What do I have to do to ensure that _pDecoder is initialized correctly?

Thank you in advance!

Helmut

We are using the Java EMA library "group: "com.refinitiv.ema", name: "ema", version: "3.9.0.1", and we encountered the following case:

The library is set up to use HMDS websockets with protocal rssl.rwf, set up such that it can reconnect like so: APAC → AMERS → EMEA

We encountered a few disconnects and reconnects, but at one point we received the following series of events/logging messages:

1. 10:54:22,220 - Channel Up From Emea
2. 10:54:22,220 - High watermark on it
3. 10:54:22,644 - "Login Denied:Failed to lookup sso token"
4. 10:54:25,654 - ERROR: loggerMsg
   ClientName: <redacted>
   Severity: Error
   Text: Failed to uninitialize OmmBaseImpl (_executor.awaitTermination() timed out).
   loggerMsgEnd
5. 10:54:25,663 - ClientName: <redacted>
   Severity: Error
   Text: Failed to close reactor channel (rsslReactorChannel).' RsslChannel='0Error Id -10Internal sysError 0Error Location ReactorChannel.closeError Text Reactor is shutdown, close aborted.'.
   loggerMsgEnd
6. 10:54:25,665 - Missing, unreadable or empty file configuration <expected as we make the config programatically>
7. 10:54:25,665 - no configuration exists in the config file for consumer dictionary <expected as we make the config programatically>
8. 10:54:25,665 - no configuration exists in the config file for consumer dictionary <expected as we make the config programatically>
9. 10:54:26,931 - Channel UP for APAC
10. 10:54:26,931 - High water mark set on the channel
11. 10:55:12,982 - Received ChannelDownReconnecting event on APAC with "Error text Connection reset"
12. 10:55:12,982 - WARN: loggerMsg
    ClientName: LoginCallbackClient
    Severity: Warning
    Text: RDMLogin stream state was changed to suspect with status message
    username <not set>
    usernameType <not set>
    State: Open/Suspect/None - text: ""
    loggerMsgEnd
13. 10:55:12,983 - WARN: loggerMsg
    ClientName: ChannelDictionary
    Severity: Warning
    Text: RDMDictionary stream was closed with status message
    streamId 3
    Reason State: Closed, Recoverable/Suspect/None - text: "channel down."
    loggerMsgEnd
14. 10:55:12,985 WARN: loggerMsg
    ClientName: ChannelDictionary
    Severity: Warning
    Text: RDMDictionary stream was closed with status message
    streamId 4
    Reason State: Closed, Recoverable/Suspect/None - text: "channel down."
    loggerMsgEnd

And then it stops. It does not retry to recreate the connection. Usually it would reconnect automatically, or continue to try, as there was another successful reconnect 4 hours before this one that had the same 4 messages at the end (points 11, 12, 13, 14).

My question is if the errors from points 4 and 5 could lead to the library not remaking the connection or something related to that?

Please feel free to ask any questions.

I’m a beginner and aiming to become proficient in LSEG SDK APIs, RTDS (Real-Time Distribution System), and Refinitiv Workspace. I’ve chosen Java as my programming language and would appreciate guidance on the following:

1. Where should I start as a complete beginner?
   • Any recommended learning path or sequence for understanding RTDS, LSEG Workspace, and SDK APIs?
2. Are there official tutorials, videos, or sample projects for EMA and ETA in Java?
   • I have access to documentation like EMAJ_DevGuide.pdf, EMAJ_Examples.pdf, and ETAJ_DevGuide.zip, but I need practical examples.
3. How do I practically learn RTDS components (ADS, ADH, DACS) and integrate them with SDK APIs?
   • Any resources or hands-on labs for ADS configuration and entitlement management?
4. What’s the best sequence for learning Refinitiv Workspace, Excel Add-in, and RDP APIs?
   • Should I start with Workspace basics or jump into API integration first?
5. Best practices for setting up a development environment (Java + Maven + RTSDK)?
   • Any tips for installation, configuration, and troubleshooting?

Scenario:
We’re simulating API loss by routing our EMA connection through a local proxy.

If the proxy is initially online and we successfully log in, everything works as expected: killing and restarting the proxy does not disrupt the connection permanently, EMA automatically restores the session.

However, if we start the application with the proxy offline, after about 45 seconds we see a login timeout, and starting the proxy after this point does not trigger reconnection. The API becomes effectively unusable.

Relevant logs during initial connection attempt (proxy offline):

13:21:39.737 [ema-api-1] TRACE com.refinitiv.ema.access.OmmConsumerImpl - loggerMsg
ClientName: ChannelCallbackClient
Severity: Trace
Text: Attempt to connect using
1] SOCKET
Channel name ALC_Primary
Instance Name PriceConsumer_1
RsslReactor @34ea22e1
InterfaceName
hostName localhost
port 14002
CompressionType None
tcpNodelay true
reconnectAttemptLimit -1
reconnectMinDelay 1000 msec
reconnectMaxDelay 5000 msec
guaranteedOutputBuffers 100
numInputBuffers 100
sysRecvBufSize 65535
sysSendBufSize 65535
connectionPingTimeout 30000 msec
initializationTimeout 5 sec

loggerMsgEnd

13:21:39.880 [ema-api-1] TRACE com.refinitiv.ema.access.OmmConsumerImpl - loggerMsg
ClientName: ChannelCallbackClient
Severity: Trace
Text: Received ChannelOpened on channel ALC_Primary
Instance Name PriceConsumer_1
loggerMsgEnd

13:21:39.882 [ema-api-1] TRACE com.refinitiv.ema.access.OmmConsumerImpl - loggerMsg
ClientName: ChannelCallbackClient
Severity: Trace
Text: Successfully created a Reactor and Channel(s)
Channel name(s) ALC_Primary
Instance Name PriceConsumer_1
loggerMsgEnd

13:21:39.887 [ema-api-1] WARN com.refinitiv.ema.access.OmmConsumerImpl - loggerMsg
ClientName: ChannelCallbackClient
Severity: Warning
Text: Received ChannelDownReconnecting event on channel ALC_Primary
RsslReactor @34ea22e1
RsslChannel @5312dd68
Error Id 0
Internal sysError 0
Error Location Reactor.processWorkerEvent
Error text Error initializing channel: errorId=-1 text=Connection refused: no further information
loggerMsgEnd

13:21:39.893 [ema-api-1] DEBUG com.yieldbroker.ema.processor.EmaPriceListener - [onStatusMsg] Received message: StatusMsg
streamId="1"
domain="Login Domain"
state="Open / Suspect / None / 'channel down'"
StatusMsgEnd

After the login timeout expires we get:

13:22:24.884 [ema-api-1] ERROR com.refinitiv.ema.access.OmmConsumerImpl - loggerMsg
ClientName: PriceConsumer_1
Severity: Error
Text: login failed (timed out after waiting 45000 milliseconds) for localhost:14002)
loggerMsgEnd13:22:24.887 [ema-api-1] ERROR com.refinitiv.ema.access.OmmConsumerImpl - loggerMsg
ClientName: ChannelCallbackClient
Severity: Error
Text: Received ChannelDown event on channel ALC_Primary
Instance Name PriceConsumer_1
RsslReactor Channel is null
Error Id 0
Internal sysError 0
Error Location null
Error text Reactor shutting down...
loggerMsgEnd

Is there a recommended way to handle initial login retries in EMA 3.9.1.1 without breaking the automatic reconnection that works after a successful login? Essentially, we want the client to keep retrying to log in until the proxy/API becomes available, but still leverage the built-in automatic recovery after login.

Thanks!