This library provides the capability to send and receive messages by connecting to the RabbitMQ server.
RabbitMQ gives your applications a common platform to send and receive messages and a safe place for your messages to live until received. RabbitMQ is one of the most popular open-source message brokers. It is lightweight and easy to deploy on-premise and in the cloud.
First, you need to set up the connection with the RabbitMQ server. The following ways can be used to connect to a RabbitMQ server.
- Connect to a RabbitMQ node with the default host and port:
rabbitmq:Client rabbitmqClient = check new(rabbitmq:DEFAULT_HOST, rabbitmq:DEFAULT_PORT);
- Connect to a RabbitMQ node with a custom host and port:
rabbitmq:Client rabbitmqClient = check new("localhost", 5672);
- Connect to a RabbitMQ node with host, port, and additional configurations:
rabbitmq:ConnectionConfiguration config = {
username: "ballerina",
password: "password"
};
rabbitmq:Client rabbitmqClient = check new("localhost", 5672, configs);
The rabbitmq:Client
can now be used to send and receive messages as described in the subsequent sections.
Client applications work with exchanges and queues, which are the high-level building blocks of the AMQP protocol. These must be declared before they can be used. The following code declares an exchange and a server-named queue and then binds them together.
check rabbitmqClient->exchangeDeclare("MyExchange", rabbitmq:DIRECT_EXCHANGE);
check rabbitmqClient->queueDeclare("MyQueue");
check rabbitmqClient->queueBind("MyQueue", "MyExchange", "routing-key");
This sample code will declare,
- a durable auto-delete exchange of the type
rabbitmq:DIRECT_EXCHANGE
- a non-durable, exclusive auto-delete queue with an auto-generated name
Next, the queueBind
function is called to bind the queue to the exchange with the given routing key.
check rabbitmqClient->exchangeDeclare("MyExchange", rabbitmq:DIRECT_EXCHANGE);
check rabbitmqClient->queueDeclare("MyQueue", { durable: true,
exclusive: false,
autoDelete: false });
check rabbitmqClient->queueBind("MyQueue", "MyExchange", "routing-key");
This sample code will declare,
- a durable auto-delete exchange of the type
rabbitmq:DIRECT_EXCHANGE
- a durable, non-exclusive, non-auto-delete queue with a well-known name
- Delete a queue:
check rabbitmqClient->queueDelete("MyQueue");
- Delete a queue only if it is empty:
check rabbitmqClient->queueDelete("MyQueue", false, true);
- Delete a queue only if it is unused (does not have any consumers):
check rabbitmqClient->queueDelete("MyQueue", true, false);
- Delete an exchange:
check rabbitmqClient->exchangeDelete("MyExchange");
- Purge a queue (delete all of its messages):
check rabbitmqClient->queuePurge("MyQueue");
To publish a message to an exchange, use the publishMessage()
function as follows:
string message = "Hello from Ballerina";
check rabbitmqClient->publishMessage({ content: message.toBytes(), routingKey: queueName });
Setting other properties of the message such as routing headers can be done by using the BasicProperties
record with the appropriate values.
rabbitmq:BasicProperties props = {
replyTo: "reply-queue"
};
string message = "Hello from Ballerina";
check rabbitmqClient->publishMessage({ content: message.toBytes(), routingKey: queueName, properties: props });
The most efficient way to receive messages is to set up a subscription using a Ballerina RabbitMQ rabbitmq:Listener
and any number of consumer services. The messages will then be delivered automatically as they arrive rather than having to be explicitly requested. Multiple consumer services can be bound to one Ballerina RabbitMQ rabbitmq:Listener
. The queue to which the service is listening is configured in the rabbitmq:ServiceConfig
annotation of the service or else as the name of the service.
- Listen to incoming messages with the
onMessage
remote method:
listener rabbitmq:Listener channelListener= new(rabbitmq:DEFAULT_HOST, rabbitmq:DEFAULT_PORT);
@rabbitmq:ServiceConfig {
queueName: "MyQueue"
}
service rabbitmq:Service on channelListener {
remote function onMessage(rabbitmq:AnydataMessage message) {
}
}
- Listen to incoming messages and reply directly with the
onRequest
remote method:
listener rabbitmq:Listener channelListener= new(rabbitmq:DEFAULT_HOST, rabbitmq:DEFAULT_PORT);
@rabbitmq:ServiceConfig {
queueName: "MyQueue"
}
service rabbitmq:Service on channelListener {
remote function onRequest(rabbitmq:AnydataMessage message) returns string {
return "Hello Back!";
}
}
The rabbitmq:AnydataMessage
record received can be used to retrieve its contents.
The message consuming is supported by mainly two types of acknowledgement modes, which are auto acknowledgements and client acknowledgements. Client acknowledgements can further be divided into two different types as positive and negative acknowledgements. The default acknowledgement mode is auto-ack (messages are acknowledged immediately after consuming). The following examples show the usage of positive and negative acknowledgements.
WARNING: To ensure the reliability of receiving messages, use the client-ack mode.
- Positive client acknowledgement:
listener rabbitmq:Listener channelListener= new(rabbitmq:DEFAULT_HOST, rabbitmq:DEFAULT_PORT);
@rabbitmq:ServiceConfig {
queueName: "MyQueue",
autoAck: false
}
service rabbitmq:Service on channelListener {
remote function onMessage(rabbitmq:AnydataMessage message, rabbitmq:Caller caller) {
rabbitmq:Error? result = caller->basicAck();
}
}
- Negative client acknowledgement:
listener rabbitmq:Listener channelListener= new(rabbitmq:DEFAULT_HOST, rabbitmq:DEFAULT_PORT);
@rabbitmq:ServiceConfig {
queueName: "MyQueue",
autoAck: false
}
service rabbitmq:Service on channelListener {
remote function onMessage(rabbitmq:AnydataMessage message) {
rabbitmq:Error? result = caller->basicNack(true, requeue = false);
}
}
The negatively-acknowledged (rejected) messages can be re-queued by setting the requeue
to true
.
Issues and Projects tabs are disabled for this repository as this is part of the Ballerina Standard Library. To report bugs, request new features, start new discussions, view project boards, etc. please visit Ballerina Standard Library parent repository.
This repository only contains the source code for the library.
-
Download and install Java SE Development Kit (JDK) version 21 (from one of the following locations).
-
Download and install Docker as follows. (The RabbitMQ library is tested with a docker-based integration test environment. The before suite initializes the docker container before executing the tests).
-
Installing Docker on Linux
Note: These commands retrieve content from the
get.docker.com
website in a quiet output-document mode and installs it.wget -qO- https://get.docker.com/ | sh
-
For instructions on installing Docker on Mac, go to Get Started with Docker for Mac.
-
For information on installing Docker on Windows, goo to Get Started with Docker for Windows.
-
Execute the commands below to build from source.
-
To build the library:
./gradlew clean build
-
To run the tests:
./gradlew clean test
-
To build the library without the tests:
./gradlew clean build -x test
-
To debug package implementation:
./gradlew clean build -Pdebug=<port>
-
To debug the library with Ballerina language:
./gradlew clean build -PbalJavaDebug=<port>
-
Publish ZIP artifact to the local
.m2
repository:./gradlew clean build publishToMavenLocal
-
Publish the generated artifacts to the local Ballerina central repository:
./gradlew clean build -PpublishToLocalCentral=true
-
Publish the generated artifacts to the Ballerina central repository:
./gradlew clean build -PpublishToCentral=true
As an open source project, Ballerina welcomes contributions from the community.
For more information, go to the contribution guidelines.
All contributors are encouraged to read the Ballerina Code of Conduct.
- For more information go to the
rabbitmq
library. - For example demonstrations of the usage, go to Ballerina By Examples.
- Chat live with us via our Discord server.
- Post all technical questions on Stack Overflow with the #ballerina tag.