...
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
Div |
---|
class | confluenceTableSmall |
---|
|
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 |
|
Wiki Markup |
---|
{div:class=confluenceTableSmall}
|| 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 |
| {{addresses}} | {{null}} | *Camel | addresses | null | Camel 2.12.3: |
* |
|connectionTimeout | 0| *Camel | connectionTimeout | 0 | Camel 2.14: |
* |
|requestedChannelMax | 0| *Camel | requestedChannelMax | 0 | Camel 2.14: |
* |
|requestedFrameMax | 0| *Camel | requestedFrameMax | 0 | Camel 2.14: |
* |
|requestedHeartbeat | 0| *Camel | requestedHeartbeat | 0 | Camel 2.14: |
* |
|sslProtocol | null | *Camel | sslProtocol | null | Camel 2.14: |
* |
|trustManager | null | *Camel | trustManager | null | Camel 2.14: |
* |
|clientProperties | null | *Camel | clientProperties | null | Camel 2.14: |
* |
|connectionFactory | null | *Camel | connectionFactory | null | Camel 2.14: |
* |
|automaticRecoveryEnabled | false | *Camel | automaticRecoveryEnabled | false | Camel 2.14: |
* |
|networkRecoveryInterval | 5000 | *Camel | networkRecoveryInterval | 5000 | Camel 2.14: |
* |
|topologyRecoveryEnabled | true | *Camel | topologyRecoveryEnabled | true | Camel 2.14: |
* |
|prefetchEnabled | false | *Camel | prefetchEnabled | false | Camel 2.14: |
* ** ** ** |
|prefetchSize | 0 | *Camel | prefetchSize | 0 | Camel 2.14: |
* |
|prefetchCount | 0 | *Camel | prefetchCount | 0 | Camel 2.14: |
* |
|prefetchGlobal | false | *Camel | prefetchGlobal | false | Camel 2.14: |
* |
{div} |
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.
...
The following headers are set on exchanges when consuming messages.
Div |
---|
class | confluenceTableSmall |
---|
|
Wiki Markup |
---|
{div:class=confluenceTableSmall}
|| Property || Value ||
| {{}} | message |
| {{message | rabbitmq.EXCHANGE_NAME
|
}} | from |
| {{from | rabbitmq.DELIVERY_TAG
|
}} | |
{div} |
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.
Div |
---|
class | confluenceTableSmall |
---|
|
Wiki Markup |
---|
{div:class=confluenceTableSmall}
|| Property || Value ||
| {{}} | message |
| {{message | rabbitmq.EXCHANGE_NAME
|
}} | to |
| {{}} | message |
| {{message | rabbitmq.PRIORITY
|
}} | message |
| {{message | rabbitmq.CORRELATIONID
|
}} | message |
| {{message | rabbitmq.MESSAGE_ID
|
}} | message |
| {{message | rabbitmq.DELIVERY_MODE
|
}} | not |
| {{}} | message |
| {{message | rabbitmq.CLUSTERID
|
}} | message |
| {{message | rabbitmq.REPLY_TO
|
}} | message |
| {{message | rabbitmq.CONTENT_ENCODING
|
}} | message |
| {{}} | message|
| {{message | rabbitmq.EXPIRATION
|
}} | message |
| {{message | rabbitmq.TIMESTAMP
|
}} | message |
| {{}} | |
{div} |
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.
...