Hi @mario.marchl,

Are you connecting to local market data infrastructure or RTO in cloud?

Either way, your application should only open one websocket connection for multiple subscriptions, as long as your network can handle the bandwidth of the streaming updates - which it can easily for 10 instruments.

When sending the second subscription request, please ensure that the ID is unique.

Hi @mario.marchl

It is not best practice to assign a new connection for each item request. The API supports the ability to handle thousands of requests per connection. Regarding the exception you received, are you requesting for the same item within the same connection? Also, is it an exception? Or did you receive a status response indicating the request was closed because the request was rejected?

Thank you for quick reply, I assume we are using in a cloud, because we are using following URLs:
provider=aws, endpoint=eu-west-1-aws-1-sm.optimized-pricing-api.refinitiv.net.

Can you tell me if following course of actions are correct.

We create webSocket connection:

         this.webSocket = websocketFactory.createSocket(this.url)
                    .addProtocol("tr_json2")
                    .addListener(new WebSocketAdapterImpl(this))
                    .addExtension(WebSocketExtension.PERMESSAGE_DEFLATE);

            this.webSocket.connectAsynchronously();

After that we have to send only one login request for all our rics:

       refinitivMessage.setId(1)
                .setDomain("Login")
                .setKey(new Key()
                        .setElements(new Elements()
                                .setApplicationId(APP_ID)
                                .setPosition(this.position)
                                .setAuthenticationToken(this.authToken)
                        ).setNameType("AuthnToken"));

And in the end, we can send our ric requests:

 message.setId(2)
                .setKey(new Key()
                        .setName(this.ricRequest.getRic())
                        .setService(SERVICE)).
setView(this.ricRequest.getFields());
        

Where 2 - should be replaced with uniq ID for each request, is it correct?

Yes, the ID has to be unique in the message:

message.setId(2)

Hello @mario.marchl

Like my colleagues @nick.zincone and @Gurpreet have said, one WebSocket connection can handle multiple subscription streams. You can find more detail about the item subscription with the Real-Time WebSocket API from the following resources:

• WebSocket API: Request Data from Server
• WebSocket API: Make a Batch Request for Multiple Items

The example for the batch request (multiple items in a single request) is the "MarketPriceBatchView.java" example available here.

Please note that the example is using the deployed RTDS connection, but the batch logic is the same on the RTO cloud connection.