State: Closed/Suspect/Usage error - text: "Login Rejected. Watchlist size of 0 for 'RSSL' connection

SelcukYAPICI

Hi,

There were no issues initially. I was able to retrieve data from RTO V2 via HTTP. However, our customer representative requested that I temporarily disable data retrieval in the software due to a planned license upgrade. After the license upgrade was completed, I restarted the software, but I started encountering the error mentioned in the title on the last line of the code below. What should I do in this case?

            ommConsumerConfig.consumerName("Consumer_1");

            ommConsumerConfig.clientId(strClientID);

            ommConsumerConfig.clientSecret(strClientSecret);

            ommConsumerConfig.tokenServiceUrlV2(tokenServiceUrlV2);

            OmmConsumer ommConsumer = EmaFactory.createOmmConsumer(ommConsumerConfig);

Details of the errors:

State: Closed/Suspect/Usage error - text: "Login Rejected. Watchlist size of 0 for 'RSSL' connection is outside of range [1,15000] supported for this ADS fanout tier for this type of connection."

at com.refinitiv.ema.access.OmmBaseImpl.ommIUExcept(OmmBaseImpl.java:1871) ~[ema-3.7.0.0.jar:emaj3.7.0.L1.all.rrg]

at com.refinitiv.ema.access.OmmBaseImpl.handleLoginReqTimeout(OmmBaseImpl.java:1685) ~[ema-3.7.0.0.jar:emaj3.7.0.L1.all.rrg]

at com.refinitiv.ema.access.OmmConsumerImpl.handleAdminDomains(OmmConsumerImpl.java:634) ~[ema-3.7.0.0.jar:emaj3.7.0.L1.all.rrg]

at com.refinitiv.ema.access.OmmBaseImpl.initialize(OmmBaseImpl.java:335) ~[ema-3.7.0.0.jar:emaj3.7.0.L1.all.rrg]

at com.refinitiv.ema.access.OmmConsumerImpl.<init>(OmmConsumerImpl.java:47) ~[ema-3.7.0.0.jar:emaj3.7.0.L1.all.rrg]

at com.refinitiv.ema.access.EmaFactory.createOmmConsumer(EmaFactory.java:237) ~[ema-3.7.0.0.jar:emaj3.7.0.L1.all.rrg]

wasin.w

Hello @SelcukYAPICI

The error message "Watchlist size of 0 for 'XXX' connection " indicates that there is something wrong with the RTO account.

Basically, each RTO ADS supports different watchlist size tiers based on consumer account permission. If a consumer connects to the wrong tier RTO endpoint, the log will be like this:

• Watchlist size of 50,000 for 'RSSL' connection is outside of range [1,15000]

This issue can be resolve by connecting to the correct tier RTO endpoint or using the Service Discovery feature to query a list of matches endpoints.

However, the watchlist size of the RTO account should not be 0 like this.

This issue cannot be resolve programmatically. I strongly suggest you contact the RTO support team via https://myaccount.lseg.com/en/productsupport website to help you with this account issue.

SelcukYAPICI

Hi @wasin.w

Thank you for the information. I spoke with my customer representative, and they informed me that the RTO watchlist size was inactive. They made the necessary adjustments to activate it. This resolved the issue, and I am now able to consume data again.