Error while running RTO: Item State: Closed / Suspect / None / 'Login stream was closed.'

anna.h

I am making a batch request and calling consumer.uninitialize() in the end as part of cleanup. I do receive prices but then I get this warning and a close message for all my items saying login stream was closed.

I am running my application on a trial license. Is this happening because I am on trial and there are no more updates and login stream closes on it's own.
Will this not happen in production , will I keep receiving prices as this is real time streaming and price should keep flowing.

What to do if this happens in production.

Oct 28, 2024 6:16:02 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 28, 2024 6:16:02 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

Inside onStatusMsg
Item Name: SEK=
Item State: Closed / Suspect / None / 'Login stream was closed.'
Data State: 2
Status Code: None
Status Text: Login stream was closed.

<!-- Outgoing Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/172.18.219.95:59446 remote=ap-southeast-1-aws-3-sm.optimized-pricing-api.refinitiv.net/18.136.145.111:14002] -->
<!-- Mon Oct 28 18:16:02 IST 2024 -->

<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<CLOSE domainType="LOGIN" streamId="1" containerType="NO_DATA" flags="0x00" dataSize="0">
    <dataBody>
    </dataBody>
</CLOSE>

Gurpreet

Hello @anna.h,

This is the expected behavior and not because you are on the trial license. You have closed the stream because the consumer was uninitialized. In a typical real time application, you shouldn't need to uninitialize the consumer object. Same consumer can be used for multiple requests.