You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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 is only needed for producers. For

Options

Unknown macro: {div}

Property

Default

Description

autoAck

true

 

queue

random uuid

 

routingKey

null

 

threadPoolSize

10

 

username

null

username in case of authenticated access

password

null

password for authenticated access

Headers

The following headers are set on exchanges during message transport.

Unknown macro: {div}

Property

Value

rabbitmq.ROUTING_KEY

 

rabbitmq.EXCHANGE_NAME

 

rabbitmq.CONTENT_TYPE

 

rabbitmq.PRIORITY

 

rabbitmq.DELIVERY_TAG

)

rabbitmq.CORRELATIONID

)

rabbitmq.MESSAGE_ID

)

rabbitmq.DELIVERY_MODE

)

rabbitmq.USERID

)

rabbitmq.CLUSTERID

)

rabbitmq.REPLY_TO

)

rabbitmq.CONTENT_ENCODING

)

rabbitmq.TYPE

)

rabbitmq.EXPIRATION

)

rabbitmq.TIMESTAMP

)

rabbitmq.APP_ID

)

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 be completed

  • No labels