Skip to main content

Installing Rabbit MQ

Install Rabbit MQ

There are many ways to install rabbit-mq as given below.

Using Homebrew

Homebrew has made the life easy to install the Rabbit-MQ in mac. Please refer below link to install the rabbit MQ.
Once it is installed, below command can be executed to start & stop rabbit MQ.
Start Rabbit MQ:
Stop Rabbit MQ:
/usr/local/opt/rabbitmq/sbin/rabbitmqctl stop

Using Docker

With docker it's very easy to install, we just need to pull the image and run it by executing simple command. Assuming you already have dcoker installed in your machine, you can install and run rabbit-mq using below steps.
Pull rabbit-mq image without management console.
docker pull rabbitmq:latest
Pull rabbit-mq image with management console. It is required to enable the UI for management console.
docker pull rabbitmq:3-management
Execute below command to run the image in container named "local_rabbitmq". It will create the container and start rabbit-mq. Latter you can run rabbit-mq by starting the container only (docker start local_rabbitmq).
docker run --hostname rabbitmq.local --name local_rabbitmq -p 15672:15672 rabbitmq:3-management
Execute below command to stop rabbit-mq container.
docker stop local_rabbitmq

Note: There could be other options also to get rabbit-mq like having it in cloud. For development also you can create some free developer account in cloud and get rabbit-mq running there.

Check management console

Enter below URL in browser to access the rabbitmq management console.
Enter guest/guest as username/password on login screen and you will se below screen upon successful login.

Verify the Virtual Host

Login to Rabbit-MQ management console (http://localhost:15672/) and go to "Admin" tab, then  click on the "Virtual Hosts" link to see the virtual host details. See the below screenshot.
rabbitmq vhost

If you see the state as "Stopped" in above screen then you need to check the logs at below location. Location may defer as per your installation.
If you find something in logs complaining about access inside "/usr/local/var/lib/rabbitmq/mnesia/" any of the subdirectory or file, then you need to stop the rabbitmq and then clean that directory using below commands in sequence. After that start the rabbitmq and check the vhost status if it running successfully. See the below steps.
  • Stop rabbit-mq.
  • /usr/local/opt/rabbitmq/sbin/rabbitmqctl stop
  • Go to below location and delete all contents with root user.
  • cd /usr/local/var/lib/rabbitmq/mnesia
    sudo rm -rf *
  • Start rabbit-mq.
  • /usr/local/opt/rabbitmq/sbin/rabbitmq-server
Now verify the localhost log in the mentioned log location and check the vhost status in Rabbit-MQ.


Popular Posts

Setting up kerberos in Mac OS X

Kerberos in MAC OS X Kerberos authentication allows the computers in same domain network to authenticate certain services with prompting the user for credentials. MAC OS X comes with Heimdal Kerberos which is an alternate implementation of the kerberos and uses LDAP as identity management database. Here we are going to learn how to setup a kerberos on MAC OS X which we will configure latter in our application. Installing Kerberos In MAC we can use Homebrew for installing any software package. Homebrew makes it very easy to install the kerberos by just executing a simple command as given below. brew install krb5 Once installation is complete, we need to set the below export commands in user's profile which will make the kerberos utility commands and compiler available to execute from anywhere. Open user's bash profile: vi ~/.bash_profile Add below lines: export PATH=/usr/local/opt/krb5/bin:$PATH export PATH=/usr/local/opt/krb5/sbin:$PATH export LDFLAGS=&

SpringBoot - @ConditionalOnProperty example for conditional bean initialization

@ConditionalOnProperty annotation is used to check if specified property available in the environment or it matches some specific value so it can control the execution of some part of code like bean creation. It may be useful in many cases for example enable/disable service if specific property is available. Below are the attributes which can be used for property check. havingValue - Provide the value which need to check against specified property otherwise it will check that value should not be false. matchIfMissing - If true it will match the condition and execute the annotated code when property itself is not available in environment. name - Name of the property to be tested. If you want to test single property then you can directly put the property name as string like "" and if you have multiple properties to test then you can put the names like {"prop.name1","prop.name2"} prefix - It can be use when you want to apply some prefix to

Why HashMap key should be immutable in java

HashMap is used to store the data in key, value pair where key is unique and value can be store or retrieve using the key. Any class can be a candidate for the map key if it follows below rules. 1. Overrides hashcode() and equals() method.   Map stores the data using hashcode() and equals() method from key. To store a value against a given key, map first calls key's hashcode() and then uses it to calculate the index position in backed array by applying some hashing function. For each index position it has a bucket which is a LinkedList and changed to Node from java 8. Then it will iterate through all the element and will check the equality with key by calling it's equals() method if a match is found, it will update the value with the new value otherwise it will add the new entry with given key and value. In the same way it check for the existing key when get() is called. If it finds a match for given key in the bucket with given hashcode(), it will return the value other

jaxb2-maven-plugin to generate java code from XSD schema

In this tutorial I will show how to generate the Java source code from XSD schema. I will use jaxb2-maven-plugin to generate the code using XSD file which will be declared in pom.xml to make it part of build, so when maven build is executed it will generate the java code using XSD. Class generation can be controlled in plugin configuration. Maven changes (pom.xml) Include below plugin in your pom.xml. Here we have done some configuration under configuration section as given below. schemaDirectory : This is the directory where I keep my schema (XSD file). outputDirectory : This is the java source location where I want to generate the Java files. If it is not given then by default it will be generate inside target folder. clearOutputDir : If this property is true then it will generate the classes on each build otherwise it will generate only if output directory is empty. <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>jaxb2-maven-plugin</art