We are getting 'OmmInvalidUsageException after updating our application with EMA library version ...

You will need a machine ID, associated password and a Client ID to get data from Refinitiv Realtime Optimized, formerly called Elektron Cloud.

Seems like you are not passing in the client ID parameter, or passing in an invalid Client ID. Please see this tutorial on how to create a Client ID for your application.

All comments

You will need a machine ID, associated password and a Client ID to get data from Refinitiv Realtime Optimized, formerly called Elektron Cloud.

Seems like you are not passing in the client ID parameter, or passing in an invalid Client ID. Please see this tutorial on how to create a Client ID for your application.

https://emea1.apps.cp.thomsonreuters.com/apps/AppkeyGenerator

Hi @Gurpreet,

I have now generated the client ID from the below link for our application.

I am passing userID, password and the generated clientID to connect as below.

consumer = EmaFactory.createOmmConsumer(config.consumerName(consumerName).username(userName).password(userPwd).clientId(clientId));

Now application is able to connect and getting rates. But I have received the below error message. Please let me know the implications of this error message and what needs to be done from our side to remove this error.

Note: Our application keep getting rates even after receiving this error message.

2020-12-03 04:29:20,068 WARN I/O dispatcher 1 loggerMsg

ClientName: ChannelCallbackClient

Severity: Warning

Text: Received Channel warning event on channel Channel_4

Instance Name Consumer_3_1

RsslReactor @21f12d69

RsslChannel @352410bd

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-2529. Will try again with user name and password.

loggerMsgEnd

Hi @Gurpreet,

Can we get any documentation or list of error types/messages that we can receive via the status message on OmmConsumerClient.onStatusMsg() callback?

It will help us to equip our application with better error handlings.

Thanks.

Does the application stop receiving updates after this error? Access token is refreshed every 5 minutes.

Can you please try to run the sample ema\examples\training\consumer\series400\ex450_MP_QueryServiceDiscovery and replicate this behavior?

I looked at your application error message again, and since you describe that it keeps on getting data - here is what is happening:

You have another application with the same credentials which is stealing the refresh token from this application. Both apps are fighting and using the password grant when the refresh grant fails. Please use credentials in one instance of the application only.

Hi @Gurpreet,

Previously I was using a different client id generated by Sunil. Now I generated a fresh clientId for my use and using it along with the same userId and password to connect.

Still I am getting the error. The error is coming only once approximately after 5 min of starting the application. But I am receiving the rates as usual even after getting that error.

I am using the same api from 3.5.1 library as I was using in lib version 3.3.0 previously. Only difference is I am passing the clientID parameter extra.

Should we continue to use the same api/data callback mechanism as we were doing with older library? Or do we have to handle it differently in this new library?

Please let us know.

I used the ServiceEndPointDiscovery api with dynamic emaconfig creation after getting the host and port information and then registering the client and consumer with takeExclusiveSignOnControl as true, I am able to connect and the said error exception is not coming. I am receiving rates as well. I have not used proxy information while registering for the service discovery.

serviceDiscovery.registerClient(EmaFactory.createServiceEndpointDiscoveryOption().username(userName).password(userPwd).clientId(clientId).transport(ServiceEndpointDiscoveryOption.TransportProtocol.TCP).takeExclusiveSignOnControl(takeExclusiveSignOnControl), endPointDiscoveryHandler);

consumer = EmaFactory.createOmmConsumer(config.consumerName(consumerName).username(userName).password(userPwd).clientId(clientId).takeExclusiveSignOnControl(takeExclusiveSignOnControl).config(configDb));

Not just client ID, you will need a new userID, password and a client ID, for your new application.

I used the ServiceEndPointDiscovery api with dynamic emaConfig creation after getting the host and port information and then registering the client and consumer with takeExclusiveSignOnControl as true, I am able to connect and the said error exception is not coming. I am receiving rates as well. I have not used proxy information while registering for the service discovery.

Is this a safe way to have a better connection experience with the new library or something else has to be done?