When we create 26th instance, we found that there is “Error: 1006 This connection has received a neg

zoe

We have the consumer config below,

            <Consumer>

                <Name value="consumer1"/>

                <ChannelSet value="Channel_1,Channel_2"/>

                <Logger value="Logger_1"/>

                <Dictionary value="Dictionary_1"/>

                <XmlTraceToStdout value="0"/>

                <LoginRequestTimeOut value="60000" />

                <ReconnectMaxDelay value="3000" />

                <ReconnectMinDelay value="1000" /-->

                <ReconnectAttemptLimit value="2400" />

                <ReconnectMaxDelay value="20000" />

                <ReconnectMinDelay value="15000" />

            </Consumer>

We create the consumer with same config and channel repeatedly in our program,

e.g

consumer = new OmmConsumer(ommConsumerCfg);

When we create 26th instance, we found that there is “Error: 1006 This connection has received a negative acknoowledgement response from the server.” in log and then retry success.

May I know what’s the reason and how to avoid this?

loggerMsg

    TimeStamp: 2024/11/26 15:17:50.624

    ClientName: ChannelCallbackClient

    Severity: Warning

    Text:    Received ChannelDownReconnecting event on channel Channel_1

    Instance Name consumer1_26

    RsslReactor 0x0xa84fa900

    RsslChannel 0x0xaea2b230

    Error Id -1

    Internal sysError 11

    Error Location /local/jenkins/workspace/RTSDK_Core_DX1/OS/RH8-64/rcdev/source/rtsdk/Cpp-C/Eta/Impl/Reactor/rsslReactorWorker.c:2244

    Error Text </local/jenkins/workspace/RTSDK_Core_DX1/OS/RH8-64/rcdev/source/rtsdk/Cpp-C/Eta/Impl/Transport/rsslSocketTransportImpl.c:6993> Error: 1006 This connection has received a negative acknoowledgement response from the server.

loggerMsgEnd

loggerMsg

    TimeStamp: 2024/11/26 15:18:05.652

    ClientName: ChannelCallbackClient

    Severity: Success

    Text:    Received ChannelUp event on channel Channel_2

    Instance Name consumer1_26

    Connected component version: ads_edge3.0.0.L2.win 64-bit (release_edge3.0.0.L4 (ssl 9d39ead 66))

loggerMsgEnd

Jirapongse

@zoe

Thank you for reaching out to us.

Did you check the server log?

You may need to contact the server team to verify the connection was rejected.

zoe

@Jirapongse

Thanks for the swift reply, does it mean LSEG side don't have any restriction on the number of instance?

And client need to check inhouse server team ?

Jirapongse

https://community.developers.refinitiv.com/discussion/comment/123039#Comment_123039

@zoe

Typically, the server can be configured to limit a number of concurrent connections created by the client.

Correct, the client needs to contact the server team to verify configurations and log files.

marcochu

https://community.developers.refinitiv.com/discussion/comment/123046#Comment_123046

Thank you for the reply. As Zoe has left the firm, I am helping to follow up on this case. Quick comment from the client:

What we doing is a kind test to found out the approx. capacity of EMA/EMS session we can establish from our application.

What we found out is , when we create >20 sessions to EMS/EMA. There is error returned (found in EMA client log)

1. As I know, we don’t able to check the log from EMS/EMA
2. The error return from EMS/EMA have error code is 1006 . (“Error: 1006 This connection has received a negative acknoowledgement response”)

• What is 1006 actually mean ?
• Does it mean we create the session too frequent?
• Any limitation of connection set in EMA/EMS?

Thank you,

Marco

Jirapongse

https://community.developers.refinitiv.com/discussion/comment/123261#Comment_123261

@marcochu

Normally Developer Community Forum is for how-to/general questions but your question seems to be more complex and requires investigation e.g. review source code, configuration, try to reproduce the problem etc. I recommend you raise a query through the premium support service.

If the client a named user of that service, the client should see a link "Contact Premium Support" when you are logged into the developer portal.

To join the premium support, the client can contact the account team or sales team directly. Otherwise, the client can raise this issue on GitHub.