EMA RSSL batch request error - RDMDictionary stream was closed with status message. streamId 4 R...

anna.h

...eason State: Closed/Suspect/None - text: "Login stream was closed."

Hi ,

I am running EMA java application for streaming real time prices using a batch request. Service discovery is working and it choses below location to connect.
ap-southeast-1-aws-3-sm.optimized-pricing-api.refinitiv.net 14002
But I get error later when consumer runs. I have already read similar posts where similar issues are posted but I am not able to figure out a solution out of the conversations. I am running on a trial license with Refinitiv

INFO: loggerMsg
    ClientName: ChannelCallbackClient
    Severity: Info
    Text:    Received ChannelUp event on channel Channel_1
Instance Name Consumer_1_1
Component Version ads3.7.2.E1.linux.rrg 64-bit
loggerMsgEnd


Oct 11, 2024 12:57:14 PM com.refinitiv.ema.access.ChannelDictionary processCallback
WARNING: loggerMsg
    ClientName: ChannelDictionary
    Severity: Warning
    Text:    RDMDictionary stream was closed with status message
streamId 3
Reason State: Closed/Suspect/None - text: "Login stream was closed."
loggerMsgEnd


Oct 11, 2024 12:57:14 PM com.refinitiv.ema.access.ChannelDictionary processCallback
WARNING: loggerMsg
    ClientName: ChannelDictionary
    Severity: Warning
    Text:    RDMDictionary stream was closed with status message
streamId 4
Reason State: Closed/Suspect/None - text: "Login stream was closed."
loggerMsgEnd

Can you help please .

Jirapongse

@anna.h

The location and names of dictionary files are defined in the EmaConfig.xml.

        <Dictionary>
            <Name value="Dictionary_2"/>
            <DictionaryType value="DictionaryType::FileDictionary"/>
            <RdmFieldDictionaryFileName value="./RDMFieldDictionary"/>
            <EnumTypeDefFileName value="./enumtype.def"/>
        </Dictionary>

You can get them from https://github.com/Refinitiv/Real-Time-SDK/tree/master/Cpp-C/etc.

Regarding the channel dictionary, you can disable log and trace in the EMA.

Can you replicate this issue (ChannelDictionary failed) with ex113_MP_SessionMgmt? If yes, please share the EMA configuration file.

Normally Developer Community Forum is for how-to/general questions but your question seems to be more complex and requires investigation e.g. review source code, configuration, try to reproduce the problem etc. I recommend you raise a query through the Contact Premium Support. You can contact your LSEG account team or sales team directly regarding Contact Premium Support.

anna.h

can someone help here please, I am running on a trial license here and have already lost a good no of days out of it.

Jirapongse

@anna.h

Thank you for reaching out to us.

Please run the ex113_MP_SessionMgmt example in the RTSDK Java package to verify what the problem is.

The example uses the Consumer_4 and Channel_4 configuarations. The Channel_4 configuration looks like this.

        <Channel>
            <Name value="Channel_4"/>
            <ChannelType value="ChannelType::RSSL_ENCRYPTED"/>
            <CompressionType value="CompressionType::None"/>
            <GuaranteedOutputBuffers value="5000"/>           
            <Host value="ap-southeast-1-aws-3-sm.optimized-pricing-api.refinitiv.net"/>
            <Port value="14002"/>
            <EnableSessionManagement value="1"/>
            <ObjectName value=""/>
        </Channel>

In the Consumer_4 configuration, please enable Tracing in the API and use the FileDictionary instead of the ChannelDictionary.

        <Consumer>
            <Name value="Consumer_4"/>
            <Channel value="Channel_4"/>
            <Dictionary value="Dictionary_2"/>
            <MaxDispatchCountApiThread value="6500"/>
            <MaxDispatchCountUserThread value="6500"/>
            <XmlTraceToStdout value="1"/>
        </Consumer>

Please share the XML trace when the problem occurred.