You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have about 500-600 clients who connect and disconnect throughout the day, however the memory consumption increases throughout the day, it appears like the socket connection is not closed or the TCP connection is not closed, due to which there's high memory usage
Memory Metrics from the deployed instance
Overview of the Rabbit MQ during the same.
From the logs of deployed cloudamqp/websocket-tcp-relay
We have about 500-600 clients who connect and disconnect throughout the day, however the memory consumption increases throughout the day, it appears like the socket connection is not closed or the TCP connection is not closed, due to which there's high memory usage
Memory Metrics from the deployed instance
Overview of the Rabbit MQ during the same.
From the logs of deployed
cloudamqp/websocket-tcp-relay2024-03-12T17:14:50.914146378Z 152.58.208.213:0 disconnected: #<IO::Error:Closed stream>
2024-03-12T17:14:52.571178383Z 152.58.208.213:0 connected
2024-03-12T17:14:52.578574932Z 152.58.208.213:0 connected to upstream
The text was updated successfully, but these errors were encountered: