EMA Java Producer not reconnecting after remote disconnect

JasonS
JasonS
in EMA

So I have created a contrbutor based on the Consummer example code (which contributes prices despite its name ... is this correct?).

The system connects corrrectly (a StatusMsg is sent and alogin request message is created and returned and that is acknowledged via a RefreshMsg)

INFO: loggerMsg
    ClientName: ChannelCallbackClient
    Severity: Info
    Text:    Received ChannelUp event on channel Channel_1
        Instance Name Consumer_1_1
        Component Version eta3.6.2.E1.linux.rrg 64-bit Static
loggerMsgEnd

INFO: StatusMsg
    streamId="5"
    domain="System Domain"
    privateStream
    state="Open / Ok / None / ''"
    name="TUNNEL1"
    serviceId="10"
    serviceName="DDS_TRCE"
StatusMsgEnd

INFO: Sending login request for user: '********'
INFO: Refresh():  isLogin=true, isStreamOpen=true, isDataOk=true
INFO: Refresh(): Login accepted - Data streaming enabled

All then goes well for many hours / days until out of the blue we get the following messages:

Aug 23, 2022 6:29:05 PM com.refinitiv.ema.access.ChannelCallbackClient reactorChannelEventCallback
WARNING: loggerMsg
    ClientName: ChannelCallbackClient
    Severity: Warning
    Text:    Received ChannelDownReconnecting event on channel Channel_1
        RsslReactor @156a1f7b
        RsslChannel @7dec2b8
        Error Id 0
        Internal sysError 0
        Error Location null
        Error text Tunnel Channel Closed
loggerMsgEnd

Aug 23, 2022 6:29:05 PM com.refinitiv.ema.access.LoginCallbackClient rdmLoginMsgCallback
WARNING: loggerMsg
    ClientName: LoginCallbackClient
    Severity: Warning
    Text:    RDMLogin stream state was changed to suspect with status message
        username <not set>
        usernameType <not set>

        State: Open/Suspect/None - text: ""
loggerMsgEnd


Aug 23, 2022 6:29:05 PM com.feed.RefinitivAdapter onStatusMsg
INFO: StatusMsg
    streamId="5"
    domain="System Domain"
    privateStream
    state="Closed, Recoverable / Suspect / None / 'channel down.'"
    name="TUNNEL1"
    serviceId="10"
    serviceName="DDS_TRCE"
StatusMsgEnd

We periodically then get the following messages

INFO: loggerMsg
    ClientName: ChannelCallbackClient
    Severity: Info
    Text:    Received ChannelUp event on channel Channel_1
        Instance Name Consumer_1_1
        Component Version eta3.6.2.E1.linux.rrg 64-bit Static
loggerMsgEnd

and then after a while

WARNING: loggerMsg
    ClientName: ChannelCallbackClient
    Severity: Warning
    Text:    Received ChannelDownReconnecting event on channel Channel_1
        RsslReactor @156a1f7b
        RsslChannel @79b17957
        Error Id 0
        Internal sysError 0
        Error Location null
        Error text Tunnel Channel Closed
loggerMsgEnd

Aug 23, 2022 6:32:21 PM com.refinitiv.ema.access.LoginCallbackClient rdmLoginMsgCallback
WARNING: loggerMsg
    ClientName: LoginCallbackClient
    Severity: Warning
    Text:    RDMLogin stream state was changed to suspect with status message
        username <not set>
        usernameType <not set>

        State: Open/Suspect/None - text: ""
loggerMsgEnd

I assumed that when the channel became available agin, there would be a corresponding StatusMsg that would request the login information again. How do we get the ChannelUp event to trigger a new StatusMsg? Or is there a much better way to ensure that the automatic reconnect occurs? Is there a specific example piece of code that I can look at (I have looked at the tutorial / example code but can't seem to see anything that is relevant)

Many thanks

Tagged:

Best Answer

  • Jirapongse
    Jirapongse
    Answer ✓

    @JasonS

    The following error could be a problem on the contribution server (RCC).

    StatusMsg
        streamId="5"
        domain="Login Domain"
        privateStream
        state="Closed / Suspect / No resources / 'System busy'"
    StatusMsgEnd

    You need to contact the Refinitiv Contributions Channel support team directly via MyRefinitiv to verify this message.

    I implemented a sample code that can recover the connection. However, it may not cover all scenarios.

    https://github.com/jirapongse-refinitiv/ContributorEMAJava




Answers

  • Jirapongse
    Jirapongse

    @JasonS

    You may check the answer to the following question regarding tunnel stream reconnection.

    I hope this will help.


  • JasonS
    JasonS

    Unfortunately that didn't help ...

    To clarify, the code I am running is based on the Contributor example which connect fine and works well, but also suffers from the same problem. To highlight the problem I have attached the output of the Contributor

    Contributing to Refinitiv Contributions Channel
    Starting encrypted connection...
    Aug 25, 2022 2:00:18 PM com.refinitiv.ema.access.ChannelCallbackClient reactorChannelEventCallback
    INFO: loggerMsg
        ClientName: ChannelCallbackClient
        Severity: Info
        Text:    Received ChannelUp event on channel Channel_1
    Instance Name Consumer_1_1
    Component Version eta3.6.2.E1.linux.rrg 64-bit Static
    loggerMsgEnd


    Created...
    Starting tunnel stream...
    -- onAllMsg --
    ----- Status message ----
    StatusMsg
        streamId="5"
        domain="System Domain"
        privateStream
        state="Open / Ok / None / ''"
        name="TUNNEL1"
        serviceId="10"
        serviceName="DDS_TRCE"
    StatusMsgEnd

    Sending client login request...
    -- onAllMsg --
    ----- Status message ----
    StatusMsg
        streamId="5"
        domain="Login Domain"
        privateStream
        state="Closed / Suspect / No resources / 'System busy'"
    StatusMsgEnd

    Aug 25, 2022 2:00:21 PM com.refinitiv.ema.access.ChannelCallbackClient reactorChannelEventCallback
    WARNING: loggerMsg
        ClientName: ChannelCallbackClient
        Severity: Warning
        Text:    Received ChannelDownReconnecting event on channel Channel_1
    RsslReactor @5f96789f
    RsslChannel @6734fcc2
    Error Id 0
    Internal sysError 0
    Error Location null
    Error text Tunnel Channel Closed
    loggerMsgEnd


    Aug 25, 2022 2:00:21 PM com.refinitiv.ema.access.LoginCallbackClient rdmLoginMsgCallback
    WARNING: loggerMsg
        ClientName: LoginCallbackClient
        Severity: Warning
        Text:    RDMLogin stream state was changed to suspect with status message
    username <not set>
    usernameType <not set>

    State: Open/Suspect/None - text: ""
    loggerMsgEnd


    -- onAllMsg --
    ----- Status message ----
    StatusMsg
        streamId="5"
        domain="System Domain"
        privateStream
        state="Closed, Recoverable / Suspect / None / 'channel down.'"
        name="TUNNEL1"
        serviceId="10"
        serviceName="DDS_TRCE"
    StatusMsgEnd

    Aug 25, 2022 2:00:23 PM com.refinitiv.ema.access.ChannelCallbackClient reactorChannelEventCallback
    INFO: loggerMsg
        ClientName: ChannelCallbackClient
        Severity: Info
        Text:    Received ChannelUp event on channel Channel_1
    Instance Name Consumer_1_1
    Component Version eta3.6.2.E1.linux.rrg 64-bit Static
    loggerMsgEnd

    While it all works fine initially, the ChannelUp never seems to generate a message (status or otherwise) so that the tunnel can be reconnected. I have added the recommendations from the other post, but they don't seem to make any difference..

  • JasonS
    JasonS
    Thanks for the example code, that really helped! (the previous article didn't cover all the elements in your example).

Categories