How to force rabbitmq to release resources?

Question

Ruby on Rails

In the project we use Rabbitmq with ruby.
RabbitMQ constantly disposes of resources and does not release them.
This concerns RAM usage and open connections.
One of two things brings the server to its knees - either RabbitMQ eats up all the memory or rests on 1024 open files in /proc
Programmers swear that there are no leaks on their part.
I could not find in the offdocs the parameters that affect the closing of open connections.
How can I force RabbitMQ to close those sockets that are no longer in use and thereby avoid the problem with open 1024 files? Maybe the program is constantly initiating new connections to the RabbitMQ server and not closing the old ones. I'm not strong in rubies, so I can't figure it out from the code.

Answer 1

Something cleared up.
The problem with 1024 open files has been resolved and is no longer relevant, but the issue of memory utilization remains open.
I found that in the rebbit the most memory is consumed on Binaries
Memory used by shared binary data in the Erlang VM. In-memory message bodies show up here.
Everything was decided by a complete update of RabbitaMQ and, importantly, Erlang'a to the latest version.
Thanks to all.