Fixed handling of system signals when waiting for a new message from the...

[TwistedLogic]

... queue. Close #178

[videlalvaro]

Can you explain the fix?

[TwistedLogic]

If you launch a consumer without the -w option, it's assumed the consumer will receive and process OS signals (SIGTERM, SIGINT, SIGHUP). If a message is currently to be processed everything works well, the message is processed and the consumer quits. When the consumer is waiting for new mesages, i.e. the queue is empty, if you send a SIGINT signal for instance, nothing happens because the BaseConsumerCommand::forceStopConsumer() method just sets the protected property $forceStop and does nothing else. The BaseConsumer::stopConsuming() method instead stops the wait on the socket, so the consumer can use the exit signal even when the queue is empty.

I'm not completely sure if there could be a message loss, can you take a look at it?

[RuslanZavacky]

@videlalvaro @TwistedLogic any news on merging it?