Warning :RSSL Connection "received message for a not registered item"

Susan Genoray

I am hoping some of the experts here can shed some light on a warning message:
Developer is seeing several of the following Warning message in his log file for the same stream;

11:57:09.869304 INF RDM/RDMClient.cpp(200)[0x7fd7877fe700] LoggerNotifyEvent from RSSL_Cons_Adapter2[Mon Jan 13 11:57:09 2014]: (ComponentName) RSSL_Cons_Adapter: (Severity) Warning: "Connection_RSSL" received message for a not registere d item: stream id = 204

11:57:09.869383 INF RDM/RDMClient.cpp(200)[0x7fd8127fc700] LoggerNotifyEvent from RSSL_Cons_Adapter2[Mon Jan 13 11:57:09 2014]: (ComponentName) RSSL_Cons_Adapter: (Severity) Warning: "Connection_RSSL" received message for a not registere d item: stream id = 204

followed by disconnect from the ADS.

11:57:09.940594 INF RDM/RDMClient.cpp(200)[0x7fd7877fe700] LoggerNotifyEvent from RSSL_Adapter1[Mon Jan 13 11:57:09 2014]: (ComponentName) RSSL_Adapter: (Severity) Information: RSSL Channel closing on connection "Default::Connection_RSSL p2psa.eur.nsroot.net:14002" due to "requested disconnect"

Has anyone come across the above warnings? Under what circumstances could a consumer client receive events for an unregistered item?

Jirapongse

Client may see this warning message when the consumer application received message (e.g. Update, Refresh) that is unexpected by the consuming application. Often, the common case for this is when the consumer receives Update/Refresh of the item that RFA has already unregistered the handle of that item.

When client requests to close/unregister the handle, RFA internally send Close Message to the provider. There can be some delay while the Close Message is being transported to the provider. During this delay period, the provider may still send down response messages( e.g. Update message) to the consumer, if this happens , RFA consumer will process these messages, but it could not match these messages to any opening stream ( due to the stream is closed by RFA , and removed from its watch list). Therefore, RFA will generate this warning message and log through RFA Logger ,and won’t forward the response messages to the application. As the matter of fact, the warning message is harmless.