The sdk will hang after ChannelDownReconnecting event and trying to reconnect. It recovers after we restart the client.
This happens only in the SDK where we cannot even catch the event to restart the instance.
Log is attached.
1
●1 ●1 ●2
exceeded maximum number of mounts per user after ChannelDownReconnecting event
reuters-api.zip
Hi @mingxuan.zhang,
Thank you for your participation in the forum.
Are any of the replies below satisfactory in resolving your query?
If yes please click the 'Accept' text next to the most appropriate reply. This will guide all community members who have a similar question.
Otherwise please post again offering further insight into your question.
Thanks,
AHS
Hi,
Please let us know if we have any update on this issue.
Feel free to post again if you have any further questions.
Regards,
AHS
Thank you for your participation in the forum.
Are any of the replies below satisfactory in resolving your query?
If yes please click the 'Accept' text next to the most appropriate reply. This will guide all community members who have a similar question.
Otherwise please post again offering further insight into your question.
Thanks,
AHS
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
AHS
9.6k
●10 ●7 ●7
Hello @mingxuan.zhang
According to the given EMA log file, your EMA application could not login successfully and got the "exceeded maximum number of mounts per user" error message. This error indicates that the number of mounts per user(the number of applications connecting/trying to login to the server) exceeds the limit set on the server.
To avoid the error, you should:
- Reduce the number of your applications connecting to this server; to reduce the number of mounts per user.
or
- Contact your Thomson Reuters account team to increase the maximum number of mounts per user on this server according to your usage.
Thank you @Pimchaya.Wongrukun.
We are not manually creating multiple sessions upon errors and rely on the API to auto recover the session while it fails and hangs up the application.
Outside the API context the application just get a status msg saying the channel is down.
17.2k
●82 ●39 ●63
Hi @mingxuan.zhang,
At first glance, it appears your application may be manually trying to open multiple connections to the server. Because we know very little about what your application is doing, it is difficult to say whether your logic will try to create multiple sessions upon failure. Doing this will attempt to open up a new connection. At some point, you do receive a "Service Up" but shortly after the error comes in.
I'm assuming you are using RFA. Are you manually creating multiple sessions upon errors you receive or are you relying on the built-in features within the API where it will automatically recover on your behalf?
Hi, @nick.zincone.1
We are not manually creating multiple sessions upon errors and rely on the API to auto recover the session.
We are using com.thomsonreuters.ema.access.OmmConsumerClient to connect to the service. We do receive a channel down
state="Open / Suspect / None / 'channel down.'"
So far we just print out the event. The consumerClient automatically do the reconnect and get this error msg and hangs the application.
State: Closed/Suspect/Login rejected, exceeded maximum number of mounts per user - text: "Exceeded maximum number of mounts per user."
loggerMsgEnd
9.6k
●10 ●7 ●7
Hello @mingxuan.zhang
If you would like your EMA application to get a status message when it fails to logs in, your application needs to register for login stream, please refer to a consumer application example330__Login__Streaming.
17.2k
●82 ●39 ●63
@mingxuan.zhang, you will need to confirm that there are no other applications or instances of your application connecting into the same server using your user credentials. You are getting rejected because the server has a limit on the number of active connections for your user credentials. You will need to get in touch with your market data team to determine what this limit is and possibly where these additional active connections are coming from.
