You may see this warning message when the consumer application receives a message (e.g. Update, Refresh) that is unexpected by RFA.

Typically, there are two scenarios which can cause this warning.

1. Request timeout. For example, RFA sends a request for a RIC, such as IBM.N with stream ID #3. However, there is no response back from the server due to some issues on the server. Then, the request is timeout in RFA so it will close the stream ID# 3 and send a new request for the same item with a new stream ID #4.

However, after closing, if there is a response sent by the server for stream ID# 3, RFA will ignore it and report it with the following message. The message will not be dispatched to the application.

(ComponentName) Static: (Severity) Warning: "Connection_RSSL" received an unexpected message. stream id = 3.

You can contact the server team to verify the problem in the infrastructure or you can increase the value of request timeout by using the following configuration:

\Connections\<ConnectionName>\requestTimeout

The default value is 45 seconds.

2. When the application requests to close/unregister the handle, RFA internally sends 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 response messages( e.g. Update message) to the consumer, if this happens, RFA will process these messages, but it cannot match these messages to any opening stream because 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 will not forward the response messages to the application.

As the matter of fact, this warning message is harmless and can be ignored.