question

Upvotes
Accepted
1 0 1 3

RSSL buffer failed

Has anyone come across this error ? It appears every time when traffic volume is high, RFA got disconnected and got this error. Any hint to indicate what might be the issue ?

INFO (FA_LOG) Publisher 0: OMM error event received: Attempt to get rssl buffer failed! Please check log for details. Client session could have already disconnected.

treprfarfa-apiOMMrsslbuffer
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

"Attempt to get rss buffer failed!".

I wonder what "rss" is or if that is just a spelling error ? Btw: You haven't specified which of the RFA APIs you are using (C++, Java, .NET).

sorry typo should be rssl buffer. API is using C++

@clapun

Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.

Thanks,
AHS

Upvotes
Accepted
52.9k 136 44 63

When publishing a message, the message is written to the internal buffer before sending it to the network. This buffer is reserved when the channel is created and its size can be configured by using the following RFA configurations for RSSL_PROV connection type.

  • bufferPoolSize
    Sets the maximum size of the buffer pool, which is shared among all server-side RSSL channels. Each RSSL Server can have its own buffer pool
  • guaranteedOutputBuffers
    Number of output buffers that are guaranteed to an RSSL channel. Once this value is reached, the channel will start using pool buffers, if available. Guaranteed output buffers are allocated on a per channel basis
  • maxOutputBuffers
    Maximum number of output buffers allowed to an RSSL channel on the server side. This is the number of guaranteed output buffers plus the number of pool buffers available to this channel

    Once this value is reached, the channel will be unable to get any new buffers until some of the currently held buffers are released

This error “Attempt to get rssl buffer failed!” indicates there are no buffers available to the API. This typically occurs because:

  • The channel has been disconnected
  • The network issue
  • The client application is a slow consumer
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
24.9k 87 10 22

Hi,

@clapun

There was a bug in RFA C++ 7.2 that was fixed in RFA C++ 7.4.0.L1 as described below:

rfasl10803;Provider may not get InactiveClientSession event when consumer is killed The provider application may not able to get InactiveClientSession event when the consumer application is killed. If the application still publishes data to inactive client, a lot of the error message "Attempt to get rssl buffer failed! Please check log for details. Client session could have already disconnected" are generated in rfa log file.

Can you confirm which version of RFA C++ you are using?

Regards,
Umer

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.