Attila Rajmund Nohl

I faced the same problem (couldn't connect to RabbitMQ), this patch and the configuration update (add the `channel_max` attribute) solves the problem. Highly useful change.

Looking at the traces now I see that the `lasp:query` call in step 1 blocks because the `lasp_distribution_backend` process is already handling a different request - it's probably coming from...

I looked more at the traces and found the following call flows leading to this deadlock: 1. A `partisan_peer_service_client` receives a TCP(?) message on a socket in a `handle_info` function....

I'd just like to add that at work we already have a similar static analyzer check: there's a separate configuration file specifying what are the API modules - and if...