Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • Elektron /
  • WebSocket API /

For a deeper look into our Elektron API, look into:

Overview |  Quickstart |  Documentation |  Downloads |  Tutorials |  Articles

avatar image
Question by pradeep.badoni · Apr 20, 2021 at 05:30 AM · websocketsrrtorefinitiv-realtime-optimised

WebSocket API - Login Rejected. Watchlist size of 0 for 'WS JSON2' connection is outside of range [1,3000] supported for this ADS fanout tier for this type of connection.

Hi Team,

I am started getting the below issue and not getting any rates.

"Login Rejected. Watchlist size of 0 for 'WS JSON2' connection is outside of range [1,3000] supported for this ADS fanout tier for this type of connection."

Could you please let me know what is the meeting of this message and how it any be resolved.

Thanks

Pradeep B

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

2 Replies

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by umer.nalla · Apr 20, 2021 at 08:39 AM

Hi @pradeep.badoni

The message 'Watchlist size of 0' suggests to me there is something wrong with your MachineID.

Based on your previous posts regarding Websocket API, it would appear that you were receiving data previously. So, is this a new MachineID or an existing one that has stopped working for you?

IF this is an existing ID, and you are using service Discovery rather than a fixed endpoint, then please raise a 'Refinitiv Real-Time - Optimized ' ticket at My.Refinitiv so the RRTO team can try and investigate why your ID has stopped working,.

If you are using a fixed endpoint then please follow the instructions in the above post my colleague mentioned and test with the Service Discovery example.

If this is a new additional MachineID, please ask your Refinitiv account manager to investigate the licences assigned to this new ID.

Comment

People who like this

0 Show 1 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

avatar image
pradeep.badoni · Apr 20, 2021 at 10:03 AM 0
Share

Hi @umer.nalla

This is an existing machine ID and I was able to import he rates with the same ID in the past and I am using the service discover mechanism.

I will reach out to My.Refinitiv

Thanks

Pradeep B

avatar image
REFINITIV
Answer by wasin.w · Apr 20, 2021 at 07:04 AM

Hello @pradeep.badoni

Which RRTO WebSocket endpoint that you are trying to connect to? Each endpoint has a different tier based on what tier you are assigned as RTTO customer. Please see more detail from the discussion in this post.

I suggest you try the Service Discovery mechanism to discover the appropriate endpoint and also provide alternative endpoints in case one is unavailable.

Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
8 People are following this question.

Related Questions

Real-Time - Optimized: Change in Service Discovery Request for WebSocket API - Ticket 13104

prefix "/" on RIC name

Web Socket API - Process implementation Confirmation

Concurrent usage EDP

C# stopped working

  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Electronic Trading
    • Generic FIX
    • Local Bank Node API
    • Trading API
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Intelligent Tagging
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open Calais
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • RDMS
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • Workspace SDK
    • Element Framework
    • Grid
  • World-Check Data File
  • 中文论坛
  • Explore
  • Tags
  • Questions
  • Badges