Regarding the RFA API, the LoggerNotifyEvent event prints the log and does not update the data

Options
liuyi
liuyi Newcomer

hello

Due to network reasons, the connection is broken, and after reconnection, the following log information appears.

The message prompts that the connection has been established, but the data has not been updated and pushed, and the log information in bold below is printed.

What are the possible problems with this type of log?

********************* ERROR!
********************** ERROR! *********************

2018 Nov 03 00:44:27.864 ST GMT+08:00 2D4
2D0 570 ERROR*


<- Received LoggerNotifyEvent:


[Sat Nov 03 00:44:27 2018]: (ComponentName) Static: (Severity) Error:
RSSL Channel read failed on connection "Default::Connection_RSSL1
**************:14002". Channel will
be closed. (Internal debug info:
"<..\..\..\Ripc\Impl\ripcsrvr.c:6654> Error:1002 ripcRead() failure.
Connection reset by peer

", errno: RSSL_RET_FAILURE [0] - )

.

******************** WARNING!
******************** WARNING! ********************

2018 Nov 03 00:44:27.864 ST GMT+08:00 2D4
2D0 570 WARN*


<- Received LoggerNotifyEvent:


[Sat Nov 03 00:44:27 2018]: (ComponentName) Static: (Severity) Warning:
RSSL Channel closing on connection "Default::Connection_RSSL1 **************:14002" due to "channel read failure"

.

2018 Nov 03 00:44:27.864 ST GMT+08:00 2D4
2D0 570 TRACE <- Received
LoggerNotifyEvent:


[Sat Nov 03 00:44:27 2018]: (ComponentName) Static: (Severity)
Information: Connection Status Changed, RSSL_Cons_Connection
"Default::Connection_RSSL1 **************:14002" State:
"Down" StatusCode: "None" StatusText: Connection down

.

2018 Nov 03 00:44:27.879 ST GMT+08:00 2D4
2D0 570 TRACE <- Received
LoggerNotifyEvent:


[Sat Nov 03 00:44:27 2018]: (ComponentName) Static: (Severity)
Information: RSSL_Cons_Connection "Default::Connection_RSSL1 **************:14002" will be tried in 15000 milliseconds

.

********************** INFO
************************ INFO **********************

2018 Nov 03 00:44:28.707 ST GMT+08:00 2D4
2D0 551 INFO


Received ConnectionEvent from Connection_RSSL1. Connection is: Down

Connection
Status Text: Connection down

Connection
Status Code: 1.

Connection
Type: RSSL

Connected
Host Name : **************

Connected
Port : 14002

Connected
Component Version :

[0]
: ezd1.2.1.L1.win.rrg 64-bit

.

********************* ERROR!
********************** ERROR! *********************

2018 Nov 03 00:44:42.786 ST GMT+08:00 2D4
2D0 570 ERROR*


<- Received LoggerNotifyEvent:


[Sat Nov 03 00:44:42 2018]: (ComponentName) Static: (Severity) Error:
RSSL Channel read failed on connection "Default::Connection_RSSL **************:14002". Channel will
be closed. (Internal debug info:
"<..\..\..\Ripc\Impl\ripcsrvr.c:6654> Error:1002 ripcRead() failure.
Connection reset by peer

", errno: RSSL_RET_FAILURE [0] - )

.

******************** WARNING!
******************** WARNING! ********************

2018 Nov 03 00:44:42.801 ST GMT+08:00 2D4
2D0 570 WARN*


<- Received LoggerNotifyEvent:


[Sat Nov 03 00:44:42 2018]: (ComponentName) Static: (Severity) Warning:
RSSL Channel closing on connection "Default::Connection_RSSL **************:14002" due to "channel read failure"

.

2018 Nov 03 00:44:42.801 ST GMT+08:00 2D4
2D0 570 TRACE <- Received
LoggerNotifyEvent:


[Sat Nov 03 00:44:42 2018]: (ComponentName) Static: (Severity)
Information: Connection Status Changed, RSSL_Cons_Connection
"Default::Connection_RSSL **************:14002" State: "Down"
StatusCode: "None" StatusText: Connection down

.

2018 Nov 03 00:44:42.801 ST GMT+08:00 2D4
2D0 570 TRACE <- Received LoggerNotifyEvent:


[Sat Nov 03 00:44:42 2018]: (ComponentName) Static: (Severity)
Information: RSSL_Cons_Connection "Default::Connection_RSSL **************:14002" will be tried in 15000 milliseconds

.

********************** INFO
************************ INFO **********************

2018 Nov 03 00:44:42.973 ST GMT+08:00 2D4
2D0 551 INFO


Received ConnectionEvent from Connection_RSSL. Connection is: Down

Connection
Status Text: Connection down

Connection
Status Code: 1.

Connection
Type: RSSL

Connected
Host Name : **************

Connected
Port : 14002

Connected
Component Version :

[0]
: ezd1.2.1.L1.linux.rrg 64-bit

.

******************** WARNING!
******************** WARNING! ********************

2018 Nov 03 00:44:42.973 ST GMT+08:00 2D4
2D0 648 WARN*


<- Received MMT_LOGIN Status - Login Pending


streamState : Open


dataState : Suspect


statusCode : None


statusText : Connection Down.

2018 Nov 03 00:44:42.989 ST GMT+08:00 2D4
2D0 570 TRACE <- Received
LoggerNotifyEvent:

[Sat
Nov 03 00:44:42 2018]: (ComponentName) Static: (Severity) Information: RSSL
channel init in progress for connection "Default::Connection_RSSL1 **************:14002".

.

2018 Nov 03 00:44:42.989 ST GMT+08:00 2D4
2D0 570 TRACE <- Received
LoggerNotifyEvent:


[Sat Nov 03 00:44:42 2018]: (ComponentName) Static: (Severity)
Information: RSSL channel connected for connection
"Default::Connection_RSSL1 **************:14002".

.

2018 Nov 03 00:44:42.989 ST GMT+08:00 2D4
2D0 570 TRACE <- Received
LoggerNotifyEvent:


[Sat Nov 03 00:44:42 2018]: (ComponentName) Static: (Severity)
Information: RSSL channel connected with "Requested version: 14.1,
Connected version: 14.0" for connection "Default::Connection_RSSL1 **************:14002".

.

2018 Nov 03 00:44:42.989 ST GMT+08:00 2D4
2D0 570 TRACE <- Received
LoggerNotifyEvent:


[Sat Nov 03 00:44:42 2018]: (ComponentName) Static: (Severity)
Information: RSSL channel on connection "Default::Connection_RSSL1 **************:14002" has negotiated ping timeout set to: 30000

.

2018 Nov 03 00:44:43.004 ST GMT+08:00 2D4
2D0 570 TRACE <- Received
LoggerNotifyEvent:


[Sat Nov 03 00:44:42 2018]: (ComponentName) Static: (Severity)
Information: Connection Status Changed, RSSL_Cons_Connection
"Default::Connection_RSSL1 **************:14002" State: "Up"
StatusCode: "None" StatusText: Connection up

.

2018 Nov 03 00:44:57.911 ST GMT+08:00 2D4
2D0 570 TRACE <- Received
LoggerNotifyEvent:


[Sat Nov 03 00:44:57 2018]: (ComponentName) Static: (Severity)
Information: RSSL channel init in progress for connection
"Default::Connection_RSSL **************:14002".

.

2018 Nov 03 00:44:57.911 ST GMT+08:00 2D4
2D0 570 TRACE <- Received
LoggerNotifyEvent:


[Sat Nov 03 00:44:57 2018]: (ComponentName) Static: (Severity) Information:
RSSL channel connected for connection "Default::Connection_RSSL **************:14002".

.

2018 Nov 03 00:44:57.911 ST GMT+08:00 2D4
2D0 570 TRACE <- Received
LoggerNotifyEvent:


[Sat Nov 03 00:44:57 2018]: (ComponentName) Static: (Severity) Information:
RSSL channel connected with "Requested version: 14.1, Connected version:
14.0" for connection "Default::Connection_RSSL **************:14002".

.

2018 Nov 03 00:44:57.926 ST GMT+08:00 2D4
2D0 570 TRACE <- Received
LoggerNotifyEvent:


[Sat Nov 03 00:44:57 2018]: (ComponentName) Static: (Severity)
Information: RSSL channel on connection "Default::Connection_RSSL **************:14002" has negotiated ping timeout set to: 30000

.

2018 Nov 03 00:44:57.926 ST GMT+08:00 2D4
2D0 570 TRACE <- Received LoggerNotifyEvent:


[Sat Nov 03 00:44:57 2018]: (ComponentName) Static: (Severity)
Information: Connection Status Changed, RSSL_Cons_Connection
"Default::Connection_RSSL **************:14002" State: "Up"
StatusCode: "None" StatusText: Connection up

.

********************** INFO
************************ INFO **********************

2018 Nov 03 00:44:59.942 ST GMT+08:00 2D4
2D0 551 INFO


Received ConnectionEvent from Connection_RSSL. Connection is: Up

Connection
Status Text: Connection up

Connection
Status Code: 1.

Connection
Type: RSSL

Connected
Host Name : **************

Connected
Port : 14002

Connected
Component Version :

[0]
: ezd1.2.1.L1.linux.rrg 64-bit

.

******************** WARNING!
******************** WARNING! ********************

2018 Nov 03 00:44:59.942 ST GMT+08:00 2D4
2D0 570 WARN*


<- Received LoggerNotifyEvent:


[Sat Nov 03 00:44:59 2018]: (ComponentName) Static: (Severity) Warning:
Connection "Connection_RSSL" does not support Pause/Resume. Pause and
Resume requests for this connection will be ignored.

.

******************** WARNING!
******************** WARNING! ********************

2018 Nov 03 00:44:59.942 ST GMT+08:00 2D4
2D0 570 WARN*


<- Received LoggerNotifyEvent:


[Sat Nov 03 00:44:59 2018]: (ComponentName) Static: (Severity) Warning:
Connection "Connection_RSSL" does not support optimized Pause/Resume.
Optimized Pause/Resume requests will be converted to individual item
Pause/Resume requests for this connection.

.

2018 Nov 03 00:44:59.957 ST GMT+08:00 2D4
2D0 644 TRACE <- Received MMT_LOGIN
Status - Login Accepted


streamState : Open


dataState : Ok


statusCode : None


statusText : Login accepted by
host **************..

********************** INFO
************************ INFO **********************

2018 Nov 03 00:45:12.520 ST GMT+08:00 2D4
2D0 551 INFO


Received ConnectionEvent from Connection_RSSL1. Connection is: Up

Connection
Status Text: Connection up

Connection
Status Code: 1.

Connection
Type: RSSL

Connected
Host Name : **************

Connected
Port : 14002

Connected
Component Version :

[0]
: ezd1.2.1.L1.win.rrg 64-bit

.

******************** WARNING!
******************** WARNING! ********************

2018 Nov 03 00:45:12.536 ST GMT+08:00 2D4
2D0 570 WARN*


<- Received LoggerNotifyEvent:


[Sat Nov 03 00:45:12 2018]: (ComponentName) Static: (Severity) Warning:
Connection "Connection_RSSL1" does not support Pause/Resume. Pause
and Resume requests for this connection will be ignored.

.

******************** WARNING!
******************** WARNING! ********************

2018 Nov 03 00:45:12.536 ST GMT+08:00 2D4
2D0 570 WARN*


<- Received LoggerNotifyEvent:


[Sat Nov 03 00:45:12 2018]: (ComponentName) Static: (Severity) Warning:
Connection "Connection_RSSL1" does not support optimized
Pause/Resume. Optimized Pause/Resume requests will be converted to individual
item Pause/Resume requests for this connection.

.

******************** WARNING! ********************
WARNING! ********************

2018 Nov 03 00:45:12.614 ST GMT+08:00 2D4
2D0 570 WARN*


<- Received LoggerNotifyEvent:


[Sat Nov 03 00:45:12 2018]: (ComponentName) Static: (Severity) Warning:
Received Source Name <ELEKTRON_CON> from Connection
<Connection_RSSL1> is same as the one from Connection
<Connection_RSSL>

.

******************** WARNING!
******************** WARNING! ********************

2018 Nov 03 00:45:12.614 ST GMT+08:00 2D4
2D0 570 WARN*


<- Received LoggerNotifyEvent:

[Sat
Nov 03 00:45:12 2018]: (ComponentName) Static: (Severity) Warning: Received
Source Name <ELEKTRON_DD> from Connection <Connection_RSSL1> is
same as the one from Connection <Connection_RSSL>

Tagged:

Best Answer

  • @liuyi

    I don't think the problem that you did not receive data related with the warning below

    This warning message in RFA Logger is the warning messages which generated by RFA when it connecting to the server and it checks and found that server does not support Pause and Resume. I'm not sure that what is the item's status/stream you receive after the server is up. Normally if the item stream state is not close and if the service you are connecting is Up again you should be able to receive data.

    .
    WARNING! WARNING!
    2018 Nov 03 00:44:59.942 ST GMT+08:00 2D4 2D0 570 WARN*
    <- Received LoggerNotifyEvent:
    [Sat Nov 03 00:44:59 2018]: (ComponentName) Static: (Severity) Warning: Connection "Connection_RSSL" does not support Pause/Resume. Pause and Resume requests for this connection will be ignored.
    .
    WARNING! WARNING!
    2018 Nov 03 00:44:59.942 ST GMT+08:00 2D4 2D0 570 WARN*
    <- Received LoggerNotifyEvent:
    [Sat Nov 03 00:44:59 2018]: (ComponentName) Static: (Severity) Warning: Connection "Connection_RSSL" does not support optimized Pause/Resume. Optimized Pause/Resume requests will be converted to individual item Pause/Resume requests for this connection.
    .

    -Have you received any directory update message after the service is Up again?

    Just the information from the rfa.log is not enough to explain why your application did not receive the data. There could be an issue from some error on EZD server as well.