Make RabbitMQ unavailability catchable about rabbitmqbundle HOT 6 CLOSED

8 months and no action here? This issue seems quite important to me, for example I want to get a MQ-free environment for the markup guy to do his stuff and not depend on anything like RabbitMQ or whatnot.
Will try to implement this somehow, maybe issue a pull request when it's ready.

from rabbitmqbundle.

Issued a PR (#105) that adds an enable_amqp parameter. The exact parameter names can be modified to maintainer's liking.

from rabbitmqbundle.

Enable / disable is good, but would be better to be able to catch a
connection error and deal with it (or ignore it) how we like.
On Mar 26, 2013 10:05 AM, "Stepan Anchugov" [email protected]
wrote:

Issued a PR (#105https://github.com/videlalvaro/RabbitMqBundle/issues/105)
that adds an enable_amqp parameter. The exact parameter names can be
modified to maintainer's liking.

—
Reply to this email directly or view it on GitHubhttps://github.com/videlalvaro/RabbitMqBundle/issues/57#issuecomment-15449813
.

from rabbitmqbundle.

@petesiss It appears to me that you can at least override the services defined in this bundle using your own wrapper classes where you could handle almost anything.
Also, I think there's a chance you can hook something up on the exception event through Symfony's event dispatcher and process it the way you want. AMQP's exception classes are namespaced in PhpAmqpLib\Exception, so it should be easy to catch and process them.

from rabbitmqbundle.

As lazy connections are now available, you can avoid the issue on pages not using RabbitMQ by setting your connection as lazy

from rabbitmqbundle.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from rabbitmqbundle.