Hello all,
We have implemented an application which creates in parallel multiple connections to the HMDS Hosted endpoints (e.g.: emea1-hosted-hmds.platform.refinitiv.com). We create between 1-5 connections.
These connections have implemented tunneling object based on UUID, as a requirement to connect to the endpoints.
We encountered an issue that seems very particular to these endpoints, as we have not encountered it using the same implementation for HMDS or RTO (but for these 2, we do not use tunneling based on UUID).
Sometimes, usually when the local internet seems to be more overloaded, only a subset of the connections/OmmConsumers we want are created, often the case being that all of them but one are created (if we try creating 2, one connects but one enters a loop of reconnecting; if we try 4, 3 connect and one enters the loop). Usually after some time, the loop would end and successfully connect, but this can take up to even 15 minutes, which has affected clients, especially those that work from home.
The loop in question would keep printing the following message:
12:54:01,555 WARN [Thread-14] OmmConsumerImpl - loggerMsg
ClientName: ChannelCallbackClient
Severity: Warning
Text: Received ChannelDownReconnecting event on channel Channel_hmds_nts_amers2-hosted-hmds.platform.refinitiv.biz_839465263_2
RsslReactor @6ae5cab5
RsslChannel @2a3add29
Error Id 0
Internal sysError 0
Error Location Reactor.processWorkerEvent
Error text Error initializing channel: errorId=-1 text=Invalid IPC Mount Opcode (0)
loggerMsgEnd
My question is if this error could be produced by the fact that we create the connections/OmmConsumers in parallel?
Is there a way to create the consumers such that his error is not encountered?
Any details regarding this error is welcomed, as we have some ideas about it, but we aren't sure if we can do anything on our side to not encounter it.
Thank you
