Book Image

Learning RabbitMQ

By : Martin Toshev
Book Image

Learning RabbitMQ

By: Martin Toshev

Overview of this book

RabbitMQ is Open Source Message Queuing software based on the Advanced Message Queue Protocol Standard written in the Erlang Language. RabbitMQ is an ideal candidate for large-scale projects ranging from e-commerce and finance to Big Data and social networking because of its ease of use and high performance. Managing RabbitMQ in such a dynamic environment can be a challenging task that requires a good understanding not only of how to work properly with the message broker but also of its best practices and pitfalls. Learning RabbitMQ starts with a concise description of messaging solutions and patterns, then moves on to concrete practical scenarios for publishing and subscribing to the broker along with basic administration. This knowledge is further expanded by exploring how to establish clustering and high availability at the level of the message broker and how to integrate RabbitMQ with a number of technologies such as Spring, and enterprise service bus solutions such as MuleESB and WSO2. We will look at advanced topics such as performance tuning, secure messaging, and the internals of RabbitMQ. Finally we will work through case-studies so that we can see RabbitMQ in action and, if something goes wrong, we'll learn to resolve it in the Troubleshooting section.
Table of Contents (18 chapters)
Learning RabbitMQ
About the Author
About the Reviewers

Problems with starting/stopping RabbitMQ nodes

Consider that you have configured a running cluster with three nodes and one of your nodes suddenly fails. When you try to bring up that node using the following:


You get the dreadful BOOT FAILED message along with an error description message of timeout_waiting_for_tables and an Erlang stacktrace, as follows:

              Starting broker...


Error description:

Log files (may contain more information):
   D:/software/RabbitMQ/rabbitmq_server-3.4.4/log/[email protected]
   D:/software/RabbitMQ/rabbitmq_server-3.4.4/log/[email protected]

Stack trace: