Hey guys, I’m currently using Poolboy to manage a pool of AMQP connections. In my unit tests, I have some that kill connections to test the service comes back. However, Poolboy dishes out dead connections because the kill in the actual connection module takes a while to bubble up to the GenServer…

I can’t quite understand your setup but you can prevent poolboy giving the worker to the next process by monitoring the worker and waiting for the :DOWN. GenServer.stop of the worker will provide this guarantee. This works because poolboy is link’ed to the worker processes, and exit signals are sent…

That’s what I’m doing now. So, I have a pool which has many workers. Each worker is a GenServer with a Connection in its state. If I kill the connection and put the worker back, then manage to check it out again soon after, the worker hasn’t yet had its :DOWN handler called, and so the next proce…

What would be really nice is if Poolboy checked for a particular function in the worker, such as an is_ready() function, where the server could check if the Connection objects PID was alive and return true or false. That would solve the issue, I think.

[image] LSylvester: That’s what I’m doing now. So, I have a pool which has many workers. Each worker is a GenServer with a Connection in its state. If I kill the connection and put the worker back, That isn’t quite the same as what I said. I said monitor the worker and wait for that go to :…

[image] LSylvester: What would be really nice is if Poolboy checked for a particular function in the worker, such as an is_ready() function, where the server could check if the Connection objects PID was alive and return true or false. That would solve the issue, I think. Would poolboy be ma…

RMQ pool issues - Poolboy dishes out dead connections

Questions & Help Questions

darnahsan October 18, 2024, 6:52am 7

I might. be facing the same issue in my application, did you get to a solution for this @LSylvester