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:
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.
If messages should be auto acknowledged
If it is true, the exchange will be deleted when it is no longer in use
If we are declaring a durable exchange (the exchange will survive a server restart)
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
Camel 2.12.2: The exchange type such as direct or topic.
Camel 2.12.3: If the bridgeEndpoint is true, the producer will ignore the message header of "rabbitmq.EXCHANGE_NAME" and "rabbitmq.ROUTING_KEY"
Camel 2.12.3: If this option is set, camel-rabbitmq will try to create connection based on the setting of option addresses. The addresses value is a string which looks like "server1:12345, server2:12345"
Camel 2.14: Connection timeout
Camel 2.14: Connection requested channel max (max number of channels offered)
Camel 2.14: Connection requested frame max (max size of frame offered)
Camel 2.14: Connection requested heartbeat (heart-beat in seconds offered)
Camel 2.14: Enables SSL on connection, accepted value are `true`, `TLS` and 'SSLv3`
Camel 2.14: Configure SSL trust manager, SSL should be enabled for this option to be effective
Camel 2.14: Connection client properties (client info used in negotiating with the server)
Camel 2.14: Custom RabbitMQ connection factory. When this option is set, all connection options (connectionTimeout, requestedChannelMax...) set on URI are not used
Camel 2.14: Enables connection automatic recovery (uses connection implementation that performs automatic recovery when connection shutdown is not initiated by the application)
Camel 2.14: Network recoverty interval in milliseconds (interval used when recovering from network failure)
Camel 2.14: Enables connection topology recovery (should topology recovery be performed?)
Camel 2.14: Enables the quality of service on the RabbitMQConsumer side, you need to specify the option of prefetchSize, prefetchCount, prefetchGlobal at the same time
Camel 2.14: The maximum amount of content (measured in octets) that the server will deliver, 0 if unlimited.
Camel 2.14: The maximum number of messages that the server will deliver, 0 if unlimited.
Camel 2.14: If the settings should be applied to the entire channel rather than each consumer
|true||Camel 2.14: If the option is true, camel declare the exchange and queue name and bind them together. If the option is false, camel won't declare the exchange and queue name on the server.|
Camel 2.14: Number of concurrent consumers when consuming from broker. (eg similar as to the same option for the JMS component).
Camel 2.14: The routing key for the dead letter exchange
Camel 2.14: The name of the dead letter exchange
Camel 2.14: The type of the dead letter exchange
Camel 2.14.1: (Producer only) Maximum number of channels used to send messages
Camel 2.14.1: (Producer only) Maximum time (in milliseconds) waiting for a channel
|null||Camel 2.15.1: the custom ArgsConfigurer instance which could be used to configure the Args map when declaring the queue.|
Camel 2.15.1: the custom ArgsConfigurer instance which could be used to configure the Args map when declaring the exchange.
Camel 2.16: Producer Only: The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. See also the requestTimeoutCheckerInterval option.
Camel 2.16: Configures how often Camel should check for timed out Exchanges when doing request/reply over RabbitMQ. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout.
Camel 2.16: If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused
|Camel 2.16.1: If true the producer will not declare and bind a queue. This can be used for directing messages via an existing routing key.|
See http://www.rabbitmq.com/releases/rabbitmq-java-client/current-javadoc/com/rabbitmq/client/ConnectionFactory.html and the AMQP specification for more information on connection options.
Custom connection factory
The following headers are set on exchanges when consuming messages.
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
|Camel 2.14.2: This is used by the consumer to control rejection of the message. When the consumer is complete processing the exchange, and if the exchange failed, then the consumer is going to reject the message from the RabbitMQ broker. The value of this header controls this behavior. If the value is false (by default) then the message is discarded/dead-lettered. If the value is true, then the message is re-queued.|
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.
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.
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.
To receive messages from a queue that is bound to an exchange A with the routing key B,
To receive messages from a queue with a single thread with auto acknowledge disabled.
To send messages to an exchange called C