Warning: 6030 in RFA log, have you seen this before?

zoya faberov

Posting this on behalf of a client,

"“Anyhow we
were to pass on the RFA API warning message that we see from time to time and
would like to understand better… simply in the rfa.log we will see

[Sun Feb 28
15:48:05 2016]: (ComponentName) RSSL_Cons_Adapter: (Severity) Warning: 6030
(Connection_RSSL0)

[Sun Feb 28
16:00:01 2016]: (ComponentName) RSSL_Cons_Adapter: (Severity) Warning: 6030
(Connection_RSSL0)"

piyasak.chansaengsai

@zoya.farberov

It seems the required message file RFA8_RSSL_Cons_Adapter.mc is missing.

The message ID 6030 is defined in the file above, as follows:

MessageId=6030
Severity=Warning
Facility=Application
SymbolicName=OMM_UCH_LOGIN_CLOSED_RECOVER_RECEIVED
Language=English
Login response with ClosedRecover stream state received from %1 server %2 with s
tatus code "%3" and status text: %4
.

So, I removed the mc file and ran a quick test by killing the dacs snkd process to get a ClosedRecover status message. I got the following log:

******************** WARNING! ******************** WARNING! ********************
2016 Mar 10 16:47:36.282 ST GMT+07:00 1D79 3E051720   463 WARN*
    <- Received LoggerNotifyEvent:
    [Thu Mar 10 16:47:36 2016]: (ComponentName) RSSL_Cons_Adapter: (Severity) Warning: 6030 (active)
.
2016 Mar 10 16:47:36.282 ST GMT+07:00 1D79 3E051720   463 TRACE <- Received LoggerNotifyEvent:
    [Thu Mar 10 16:47:36 2016]: (ComponentName) RSSL_Adapter: (Severity) Information: 10105 (Default::Connection_RSSL apis33:14002)
.
2016 Mar 10 16:47:36.282 ST GMT+07:00 1D79 3E051720   463 TRACE <- Received LoggerNotifyEvent:
    [Thu Mar 10 16:47:36 2016]: (ComponentName) RSSL_Cons_Adapter: (Severity) Information: 6015 (Default::Connection_RSSL apis33:14002)
.
2016 Mar 10 16:47:36.282 ST GMT+07:00 1D79 3E051720   463 TRACE <- Received LoggerNotifyEvent:
    [Thu Mar 10 16:47:36 2016]: (ComponentName) RSSL_Cons_Adapter: (Severity) Information: 6011 (Default::Connection_RSSL apis33:14002)

Below is the log file when the mc file exists.

******************** WARNING! ******************** WARNING! ********************
2016 Mar 10 16:46:36.793 ST GMT+07:00 1D66 29A93720   463 WARN*
    <- Received LoggerNotifyEvent:
    [Thu Mar 10 16:46:36 2016]: (ComponentName) RSSL_Cons_Adapter: (Severity) Warning: Login response with ClosedRecover stream state received from active server Connection_RSSL with status code "RSSL_SC_DACS_DOWN" and status text: A21: Connection to DACS down, users not allowed to connect. Rssl msg state code: 29.
.
2016 Mar 10 16:46:36.794 ST GMT+07:00 1D66 29A93720   463 TRACE <- Received LoggerNotifyEvent:
    [Thu Mar 10 16:46:36 2016]: (ComponentName) RSSL_Adapter: (Severity) Information: RSSL Channel closing on connection "Default::Connection_RSSL apis33:14002" due to "close recover received from server"
.
2016 Mar 10 16:46:36.794 ST GMT+07:00 1D66 29A93720   463 TRACE <- Received LoggerNotifyEvent:
    [Thu Mar 10 16:46:36 2016]: (ComponentName) RSSL_Cons_Adapter: (Severity) Information: Connection Status Changed, RSSL_Cons_Connection "Default::Connection_RSSL apis33:14002" State: "Down" StatusCode: "None" StatusText: Connection down
.
2016 Mar 10 16:46:36.794 ST GMT+07:00 1D66 29A93720   463 TRACE <- Received LoggerNotifyEvent:

So, please verify if the mc file RFA8_RSSL_Cons_Adapter.mc is located in the working directory. The file name may start with RFA7, if the version of RFA is 7.x.

Hope this helps.

Piyasak