Hi @banerjees

Based on your reply it does indeed appear that the API is trying to renew refresh tokens for a previous Consumer instance - and supports my suspicion that you may have come across a bug with the API - which would require more detailed investigation offline.

Therefore, I recommend you contact colleagues who have an RDC account raise a Support Ticket in order to carry out further investigation of your issue.

If the above colleagues are not in your team or unable to raise a ticket for you, then you can post a summary of the issue directly on the Elektron SDK GitHub page - however, this may take longer for a response.

When you raise an RDC ticket, please include responses to the other questions I asked above including same/different MachineID + also include XML trace to help the investigation. If you post your issue on Github you can hold back the XML trace until someone reaches out to you via Github.

Hi @banerjees

Firstly are you able to recreate this by modifying a simple example such as - example113__MarketPrice__SessionManagement?

When you logout and relogin - is this with the same user/machineID or different ID?

When you remove the uninitialize call , does the new OmmConsumer instance work (i.e. allow you to consume data)?

Do you use the same OmmConsumerConfig instance each time you call createOmmConsumer or do you create a new config instance each time also?

Also, is there a particular reason why you are logging in and logging of several times within the lifecycle of the application? Please explain your requirement - as there may be a more efficient way of implementing this.

It may also help if you capture the Low level XML Trace between the application and server to see what is happening behind the scenes - and post here as .txt after removing any credential information.

https://community.developers.refinitiv.com/questions/6439/how-to-enable-tracing-incomingoutgoing-messages-em.html

On the face of it, I suspect that you may have unearthed a bug with the API and this issue may require offline investigation via RDC but we can decide that later.

Hi Umer,

Our application at Integral is a multiadaptor application which can host multiple adaptors at any point of time. So if want to take down Reuter Elektron adaptor at any point of time, we do a logout of that adaptor and then login again as and when required.

At the time of logout, we are destroying the instance of OMMConsumer object and OMMConsumer config instance and creating a new intsance each time when we do the login again.

If we are calling the consumer.uninitialize() at the time of logout, then at the time of next login our application is receiving the Channel_Up event for the new consumer object created but immediately after we are getting OmmException and login is not happening.

If we are not calling he consumer.uninitialize() at the time of logout, then at the time of next login, login is happening properly and everything works properly.

But in this case we are continuously seeing the below exceptions being posted.

2020-01-24 06:34:40,678 WARN I/O dispatcher 5 OmmConsumerImpl loggerMsg

ClientName: ChannelCallbackClient

Severity: Warning

Text: Received Channel warning event on channel Channel_4

Instance Name Consumer_3_3

RsslReactor @21e8abe9

RsslChannel @5d95ecf6

Error Id 0

Internal sysError 0

Error Location null

Error text Failed to request authentication token with refresh token for user: GE-A-00336937-3-2527. Will try again with user name and password.

loggerMsgEnd

In this case, it seems that Reuter is holding the consumer instance last created by our application (In this case Consumer_3_3) and trying to do the login again even if our application already logins itself with another consumer instance (Consumer_3_4).