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

Property	Default	Description
`autoAck`	`true`	If messages should be auto acknowledged
`autoDelete`	`true`	If it is true, the exchange will be deleted when it is no longer in use
`durable`	`true`	If we are declaring a durable exchange (the exchange will survive a server restart)
`queue`	`random uuid`	The queue to receive messages from
`routingKey`	`null`	The routing key to use when binding a consumer queue to the exchange. For producer routing keys, you set the header (see header section)
`threadPoolSize`	`10`	The consumer uses a Thread Pool Executor with a fixed number of threads. This setting allows you to set that number of threads.
`username`	`null`	username in case of authenticated access
`password`	`null`	password for authenticated access
`vhost`	`/`	the vhost for the channel
`exchangeType`	`direct`	Camel 2.12.2: The exchange type such as direct or topic.
`bridgeEndpoint`	`false`	Camel 2.12.3: If the bridgeEndpoint is true, the producer will ignore the message of rabbitmq.EXCHANGE_NAME
`addresses`	`null`	Camel 2.12.3: If this option is set, camel-rabbitmq will try to create connection based o n the setting of option addresses. The addresses value is a string which looks like "server1:12345, server2:12345"

Property	Default	Description
`autoAck`	`true`	If messages should be auto acknowledged
`autoDelete`	`true`	If it is true, the exchange will be deleted when it is no longer in use
`durable`	`true`	If we are declaring a durable exchange (the exchange will survive a server restart)
`queue`	`random uuid`	The queue to receive messages from
`routingKey`	`null`	The routing key to use when binding a consumer queue to the exchange. For producer routing keys, you set the header (see header section)
`threadPoolSize`	`10`	The consumer uses a Thread Pool Executor with a fixed number of threads. This setting allows you to set that number of threads.
`username`	`null`	username in case of authenticated access
`password`	`null`	password for authenticated access
`vhost`	`/`	the vhost for the channel
`exchangeType`	`direct`	Camel 2.12.2: The exchange type such as direct or topic.
`bridgeEndpoint`	`false`	Camel 2.12.3: If the bridgeEndpoint is true, the producer will ignore the message header of "rabbitmq.EXCHANGE_NAME" and "rabbitmq.ROUTING_KEY"
`addresses`	`null`	Camel 2.12.3: If this option is set, camel-rabbitmq w ill try to create connection based on the setting of option addresses. The addresses value is a string which looks like "server1:12345, server2:12345"

Headers

Property	Value
`rabbitmq.ROUTING_KEY`	The routing key that was used to receive the message, or the routing key that will be used when producing a message
`rabbitmq.EXCHANGE_NAME`	The exchange the message was received from
`rabbitmq.DELIVERY_TAG`	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.