Receiving close message

Randomly receiving a close message after the application is running for an hour or so. The xml trace indicates the the stream was closed even though this close is not initiated by the application.

</dataBody>

</closeMsg>

Any help to understand the problem would be of great.

Thanks,

Ketul

Find more posts tagged with

ema-api

#technology

Accepted answers

Jirapongse

@ketul.barot

The login close message is sent by the API or application. Typically, the OmmConsumer will send the login close message when it is uninitialized or destructed.

For example, the following code deletes the OmmConsumer after running for 5 seconds.

try { 
        AppClient client;
        OmmConsumer* _pConsumer = new OmmConsumer( OmmConsumerConfig().host("localhost:9998").username("user"));
        UInt64 handle = _pConsumer->registerClient( ReqMsg().serviceName( "DIRECT_FEED" ).name( "JPY=" ), client );
     
            sleep(5000);                // API calls onRefreshMsg(), onUpdateMsg(), or onStatusMsg()
         
            delete _pConsumer;
            sleep(100000);
}

The trace log will show that the API sent the login close message to the server.

<!-- Outgoing Message (Channel IPC descriptor = 260) -->
<!-- Time: 12:01:43:244 -->
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<closeMsg domainType="RSSL_DMT_LOGIN" streamId="1" containerType="RSSL_DT_NO_DATA" flags="0x0" dataSize="0">
    <dataBody>
    </dataBody>
</closeMsg>

Please make sure the OmmConsumer wasn't destructed or the application didn't send the login close message by using the login handle.

All comments

Gurpreet

Hi @ketul.barot,

Can you tell us little bit more about the application -

1. Is it a new application, and has been running in the past?

2. What infrastructure are you connecting to - local RTMDS or RTO cloud?

A close on the login stream typically means that your session has expired. Is something else happening to the application at that instance?

ketul.barot

Hi @Gurpreet ,

Application has been running in the past.

Connecting to local RTMDS.

The session is active for an hour or so and then suddenly receive the closeMsg nothing else happening. This is the login request message I sent,

</elementList>

</attrib>

</key>

</dataBody>

</requestMsg>

And this is the refresh message,

</elementList>

</attrib>

</key>

</dataBody>

</refreshMsg>

Gurpreet

Hi @ketul.barot,

Nothing exceptional is evident from these API log messages. Can you request your market data administrator to enable the logs on the ADS, so that we can see why your app gets logged out.

For the sake of test, can you please use one of the basic EMA example applications like 100 Consumer and see if the behavior is same, and the example receives a login closed message as well.

Jirapongse

@ketul.barot

The login close message is sent by the API or application. Typically, the OmmConsumer will send the login close message when it is uninitialized or destructed.

For example, the following code deletes the OmmConsumer after running for 5 seconds.

try { 
        AppClient client;
        OmmConsumer* _pConsumer = new OmmConsumer( OmmConsumerConfig().host("localhost:9998").username("user"));
        UInt64 handle = _pConsumer->registerClient( ReqMsg().serviceName( "DIRECT_FEED" ).name( "JPY=" ), client );
     
            sleep(5000);                // API calls onRefreshMsg(), onUpdateMsg(), or onStatusMsg()
         
            delete _pConsumer;
            sleep(100000);
}

The trace log will show that the API sent the login close message to the server.

<!-- Outgoing Message (Channel IPC descriptor = 260) -->
<!-- Time: 12:01:43:244 -->
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<closeMsg domainType="RSSL_DMT_LOGIN" streamId="1" containerType="RSSL_DT_NO_DATA" flags="0x0" dataSize="0">
    <dataBody>
    </dataBody>
</closeMsg>

Please make sure the OmmConsumer wasn't destructed or the application didn't send the login close message by using the login handle.

ketul.barot

@Jirapongse Yes indeed my application was exiting and that was destructing OmmConsumer. Fixed the application exit and it resolved the issue. Thanks everyone for the help

EXPLORE OUR SITES