THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
RabbitMQ Component
Available as of Camel 2.12
The rabbitmq: component allows you produce and consume messages from RabbitMQ
instances. Using the RabbitMQ AMQP client, this component offers a pure RabbitMQ approach over the generic amqp: component.
Maven users will need to add the following dependency to their pom.xml for this component:
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-rabbitmq</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
URI format
rabbitmq:http://hostname[:port]/exchangeName?[options...]://name[?options]
Where hostname is the hostname of the running rabbitmq instance or cluster. Port is optional and if not specified then defaults to the RabbitMQ client default (5672). The exchange name determines which exchange produced messages will sent to. In the case of consumers, the exchange name determines which exchange the queue will bind to.
Options
Unknown macro: {div}
Property |
Default |
Description |
|---|---|---|
|
|
If messages should be auto acknowledged |
|
|
The queue to receive messages from |
|
|
The routing key to use when binding a consumer queue to the exchange. For producer routing keys, you set the header (see header section) |
|
|
The consumer uses a Thread Pool Executor with a fixed number of threads. This setting allows you to set that number of threads. |
|
|
username in case of authenticated access |
|
|
password for authenticated access |
|
|
the vhost for the channel |
Headers
The following headers are set on exchanges when consuming messages.
Unknown macro: {div}
Property |
Value |
|---|---|
|
The routing key that was used to receive the message, or the routing key that will be used when producing a message |
|
The exchange the message was received from |
|
The rabbitmq delivery tag of the received message |
The following headers are used by the producer. If these are set on the camel exchange then they will be set on the RabbitMQ message.
Unknown macro: {div}
Property |
Value |
|---|---|
|
The routing key that will be used when sending the message |
|
The exchange the message was received from, or sent to |
|
The contentType to set on the RabbitMQ message |
|
The priority header to set on the RabbitMQ message |
|
The correlationId to set on the RabbitMQ message |
|
The message id to set on the RabbitMQ message |
|
If the message should be persistent or not |
|
The userId to set on the RabbitMQ message |
|
The clusterId to set on the RabbitMQ message |
|
The replyTo to set on the RabbitMQ message |
|
The contentEncoding to set on the RabbitMQ message |
|
The type to set on the RabbitMQ message |
|
The expiration to set on the RabbitMQ message |
|
The timestamp to set on the RabbitMQ message |
|
The appId to set on the RabbitMQ message |
Headers are set by the consumer once the message is received. The producer will also set the headers for downstream processors once the exchange has taken place. Any headers set prior to production that the producer sets will be overriden.
Message Body
The component will use the camel exchange in body as the rabbit mq message body. The camel exchange in object must be convertible to a byte array. Otherwise the producer will throw an exception of unsupported body type.
Samples
To receive messages from a queue that is bound to an exchange A with the routing key B,
from("rabbitmq://localhost/A?routingKey=B")
To receive messages from a queue with a single thread with auto acknowledge disabled.
from("rabbitmq://localhost/A?routingKey=B&threadPoolSize=1&autoAck=false")
To send messages to an exchange called C
...to("rabbitmq://localhost/B")