Getting no channels available at the end of test cases execution.

[mathiramu]

---

[lukebakken]

More than likely you have a bug in your test case code. Perhaps you are not closing channels as expected. RabbitMQ does a have a per-connection channel limit. What is logged by RabbitMQ when this happens?

If you can reliably reproduce this, please provide code so that we can do the same. Thanks.

[michaelklishin]

Monitoring channel churn and totals will provide useful data points. So will server logs and a traffic capture.

This message is not logged by RabbitMQ but rather by a client, presumably this one. Our team uses php-amqplib in our tutorials and maintains it to some extent. We are not familiar with php-amqp and IIRC it is based on a C library, which makes analyzing its behavior significantly more difficult.

[mathiramu]

---

[lukebakken]

Cannot declare or bind RabbitMQ queue "" to the exchange point. Driver error: AMQPException: Library error: connection closed unexpectedly in

Your RabbitMQ log file should show why the connection was closed unexpectedly. Please find the log lines that correspond to this.

[michaelklishin]

The log entries @lukebakken is referring to are documented in Connection Lifecycle Events.

[mathiramu]

---

[michaelklishin]

According to these logs, your application (or library) closes connections about 20 ms after opening them, cleanly. My best guess is that this is a race condition between this "connection management" by the library and what your own code does.

Such use cases are considered to be problematic and pathological: RabbitMQ and the messaging protocols it supports expect connections to be reasonably long-lived.
Consider using a specialized proxy to avoid it since this is the only known way for PHP programming model to use RabbitMQ.

Consider using php-amqplib, a well known, widely used, well maintained pure PHP client instead of what you use on top of librabbitmq-c.

[michaelklishin]

This post explains how clients negotiate connection settings and open a connection, and what this proxy does to drastically decrease the overhead of short-lived connections on PHP applications.