Rascal stop sending messages - ResourceRequest timed out

Hi Team,

Firstly, thanks so much for your library.

Just wondering if you can point me in the right direction with the following error -

TimeoutError: ResourceRequest timed out
    at ResourceRequest._fireTimeout (/home/app/node_modules/generic-pool/lib/ResourceRequest.js:62:17)
    at Timeout.bound (/home/app/node_modules/generic-pool/lib/ResourceRequest.js:8:15)
    at listOnTimeout (node:internal/timers:556:17)
    at processTimers (node:internal/timers:499:7)

We are using version 14.4.0 of Rascal to connect to RabbitMQ 3.10 on Kubernetes. RabbitMQ was deployed using a the RabbitMq Kubernetes operator.

We are currently experiencing a strange issue with one of our customers. Every 5-7 days their application container stops sending messages to all RabbitMQ queues until it is restarted. When this happens, the error above starts appearing in the logs. We have a number of different tenants connected to the same RabbitMQ cluster and they do not appear to be experiencing this issue.

At this stage we are not sure why Generic Pool is raising this error and how to reproduce it on demand.

All we know is that when this starts occurring. Rascal stops sending message to RabbitMQ until we restart the container. All pending message are lost.

Regards, Tarek

[thaoula]

@cressie176 at the moment it has not reoccured. So let’s close this issue. If it happens again we can re-open.

Once again, I really appreciate your assistance with this issue.

[cressie176]

Thanks for getting back to me @thaoula