Signals not handled when the queue is empty

[greg0ire]

When I try to send a signal to a consumer with an empty queue, it is not taken into account until a message arrives and is completely processed. I tried with SIGINT and SIGTERM. I'm using v1.3.2, and running the rabbitmq:consumer command without any flag (especially not -w because I don't want to interrupt a consumer that processes a message).

[greg0ire]

Looks like it is a regression of #89

[sergiuszm]

@videlalvaro Is there any possibility to implement https://github.com/videlalvaro/RabbitMqBundle/issues/89#issuecomment-27396755 solution to handle signals on empty queue?

[videlalvaro]

@sergiuszm do you think this will affect performance?

[sergiuszm]

@videlalvaro Yes, it could affect performance, because a lot of code need to be executed all the time. I have found better place to dispatch signals: https://github.com/videlalvaro/php-amqplib/blob/master/PhpAmqpLib/Wire/IO/StreamIO.php#L68 This code will be executed till new message in query appear.

What do you think? It should not affect performance so much but could be really helpfull with demonizing consumer process.

[videlalvaro]

Mmm… I'm not sure how code there won't affect performance

[sergiuszm]

It will - but do you have any other idea how to handle posix signals?

[videlalvaro]

What if someone creates a class for consumers to specifically do that, extending the current consumer from the bundle? Then if you have a perf penalty, you know in advance, otherwise just use the plain old consumer

[sergiuszm]

Extending current consumer will not resolve the case - it won't work because if queue is empty only code placed in while loop in https://github.com/videlalvaro/php-amqplib/blob/master/PhpAmqpLib/Wire/IO/StreamIO.php#L68 will be executed :(

[videlalvaro]

Then I'd guess the php-amqplib needs some redesign on that area to support this

[sergiuszm]

I agree. For now a quick solutions for that is to put a special message in to the rabbitmq queue and handle it in consumer service.