Disconnection of consumer from Test Provider

chamindaa
chamindaa
in ETA

We have a consumer application running with a test provider. After sending the source directory request message, the test provider responds with a source directory refresh message and the connection gets terminated. The consumer channel log always contain the following text at the end.

<!-- Channel Closed (Channel IPC descriptor = 67) -->

Can we safely assume that this implies that the disconnection was initiated from provider side?

Tagged:

Best Answer

  • veerapath.rungruengrayubkul
    veerapath.rungruengrayubkul
    Answer ✓

    I have compared the message received in EMA trace log between disconnection initialed from provider side and consumer side. The Channel Closed message is different, so this can be used to identify the disconnection side.

    Closed by provider side: 

    <!-- Channel Closed (Channel IPC descriptor = 208) -->

    Closed by consumer side:

    <!-- rsslCloseChannel Connection closed (Channel IPC descriptor = 212) -->

    However, I would suggest you verify the "ChannelCallbackClient" information in the EMA logger file. The "ChannelCallbackClient" should provide more detailed about the disconnection. Please note that the logger needs to be configured to have LoggerSeverity=LoggerSeverity::verbose.

    Below is the sample of disconnection initiated from provider side

    loggerMsg
        TimeStamp: 16:09:40.481
        ClientName: ChannelCallbackClient
        Severity: Warning
        Text:    Received ChannelDownReconnecting event on channel Channel_1
    	Instance Name Consumer_1_1
    	RsslReactor 0x00000000003F7860
    	RsslChannel 0x00000000003F7860
    	Error Id -1
    	Internal sysError 0
    	Error Location ..\..\..\ValueAdd\Reactor\Impl\rsslReactor.c:3132
    	Error Text <..\..\..\Ripc\Impl\ripcsrvr.c:6811> Error:1002 ripcRead() failure. Connection reset by peer
    loggerMsgEnd

Categories