[CONF] Apache Camel RabbitMQ
willem jiang edited the page: RabbitMQ Comment: CAMEL-7552 ... 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)
[CONF] Apache Camel RabbitMQ
willem jiang edited the page:
RabbitMQ
Comment: CAMEL-7422
...
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 rabbitmq.EXCHANGE_NAME and rabbitmq.ROUTING_KEY |
| {{addresses}} | {{null}} | *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|
|connectionTimeout| 0| *Camel 2.14:* Connection timeout|
|requestedChannelMax | 0| *Camel 2.14:* Connection requested channel max (max number of channels offered)|
|requestedFrameMax| 0| *Camel 2.14:* Connection requested frame max (max size of frame offered)|
|requestedHeartbeat | 0| *Camel 2.14:* Connection requested heartbeat (heart-beat in seconds offered)|
|sslProtocol | null | *Camel 2.14:* Enables SSL on connection, accepted value are `true`, `TLS` and 'SSLv3`|
|trustManager | null | *Camel 2.14:* Configure SSL trust manager, SSL should be enabled for this option to be effective|
|clientProperties | null | *Camel 2.14:* Connection client properties (client info used in negotiating with the server)|
|connectionFactory| null | *Camel 2.14:* Custom RabbitMQ connection factory. When this option is set, all connection options (connectionTimeout, requestedChannelMax...) set on URI are not used|
|automaticRecoveryEnabled | false | *Camel 2.14:* Enables connection automatic recovery (uses connection implementation that performs automatic recovery when connection shutdown is not initiated by the application)|
|networkRecoveryInterval | 5000 | *Camel 2.14:* Network recoverty interval in milliseconds (interval used when recovering from network failure)|
|topologyRecoveryEnabled | true | *Camel 2.14:* Enables connection topology recovery (should topology recovery be performed?)|
|prefetchEnabled | false | *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|
|prefetchSize | 0 | *Camel 2.14:* The maximum amount of content (measured in octets) that the
[CONF] Apache Camel RabbitMQ
willem jiang edited the page:
RabbitMQ
Comment: CAMEL-7384
...
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 rabbitmq.EXCHANGE_NAME and rabbitmq.ROUTING_KEY |
| {{addresses}} | {{null}} | *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|
|connectionTimeout| 0| *Camel 2.14:* Connection timeout|
|requestedChannelMax | 0| *Camel 2.14:* Connection requested channel max (max number of channels offered)|
|requestedFrameMax| 0| *Camel 2.14:* Connection requested frame max (max size of frame offered)|
|requestedHeartbeat | 0| *Camel 2.14:* Connection requested heartbeat (heart-beat in seconds offered)|
|sslProtocol | null | *Camel 2.14:* Enables SSL on connection, accepted value are `true`, `TLS` and 'SSLv3`|
|trustManager | null | *Camel 2.14:* Configure SSL trust manager, SSL should be enabled for this option to be effective|
|clientProperties | null | *Camel 2.14:* Connection client properties (client info used in negotiating with the server)|
|connectionFactory| null | *Camel 2.14:* Custom RabbitMQ connection factory. When this option is set, all connection options (connectionTimeout, requestedChannelMax...) set on URI are not used|
|automaticRecoveryEnabled | false | *Camel 2.14:* Enables connection automatic recovery (uses connection implementation that performs automatic recovery when connection shutdown is not initiated by the application)|
|networkRecoveryInterval | 5000 | *Camel 2.14:* Network recoverty interval in milliseconds (interval used when recovering from network failure)|
|topologyRecoveryEnabled | true | *Camel 2.14:* Enables connection topology recovery (should topology recovery be performed?)|
{div}
See
[CONF] Apache Camel RabbitMQ
willem jiang edited the page:
RabbitMQ
...
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 rabbitmq.EXCHANGE_NAME and rabbitmq.ROUTING_KEY |
| {{addresses}} | {{null}} | *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|
{div}
...
View Online Like View Changes
Stop watching space Manage Notifications
This message was sent by Atlassian Confluence 5.0.3, Team Collaboration Software
[CONF] Apache Camel RabbitMQ
willem jiang edited the page:
RabbitMQ
Comment: CAMEL-6868
...
Maven users will need to add the following dependency to their pom.xml for this component:
Code Block
xml
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-rabbitmq/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
URI format
Code Block
rabbitmq://hostname[:port]/exchangeName?[options]
...
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
[CONF] Apache Camel RabbitMQ
RabbitMQ
Page edited by willem jiang
Comment:
CAMEL-6809
Changes (1)
...
| {{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 |
{div}
...
Full Content
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
groupIdorg.apache.camel/groupId
artifactIdcamel-rabbitmq/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
URI format
rabbitmq://hostname[:port]/exchangeName?[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
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
Headers
The following headers are set on exchanges when consuming messages.
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.
Property
Value
rabbitmq.ROUTING_KEY
The routing key that will be used when sending the message
rabbitmq.EXCHANGE_NAME
The exchange the message was received from, or sent to
rabbitmq.CONTENT_TYPE
The contentType to set on the RabbitMQ message
rabbitmq.PRIORITY
The priority header to set on the RabbitMQ message
rabbitmq.CORRELATIONID
The correlationId to set on the RabbitMQ message
rabbitmq.MESSAGE_ID
The message id to set on the RabbitMQ message
rabbitmq.DELIVERY_MODE
If the message should be persistent or not
rabbitmq.USERID
The userId to set on the RabbitMQ message
rabbitmq.CLUSTERID
The clusterId to set on the RabbitMQ message
rabbitmq.REPLY_TO
The replyTo to set on the RabbitMQ message
rabbitmq.CONTENT_ENCODING
The contentEncoding to set on the RabbitMQ message
rabbitmq.TYPE
The type to set on the RabbitMQ message
rabbitmq.EXPIRATION
The expiration to set on the RabbitMQ message
rabbitmq.TIMESTAMP
The timestamp to set on the RabbitMQ message
rabbitmq.APP_ID
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
[CONF] Apache Camel RabbitMQ
RabbitMQ
Page edited by willem jiang
Comment:
CAMEL-6846
Changes (2)
...
|| Property || Default || Description || | {{autoAck}} | {{true}} | If messages should be auto acknowledged |
| {{autoDelete}} | {{true}} | If it is true, the message will be deleted when it is consumed | | {{durable}} | {{true}} | If message is durable |
| {{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) |
...
Full Content
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
groupIdorg.apache.camel/groupId
artifactIdcamel-rabbitmq/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
URI format
rabbitmq://hostname[:port]/exchangeName?[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
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.
Headers
The following headers are set on exchanges when consuming messages.
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.
Property
Value
rabbitmq.ROUTING_KEY
The routing key that will be used when sending the message
rabbitmq.EXCHANGE_NAME
The exchange the message was received from, or sent to
rabbitmq.CONTENT_TYPE
The contentType to set on the RabbitMQ message
rabbitmq.PRIORITY
The priority header to set on the RabbitMQ message
rabbitmq.CORRELATIONID
The correlationId to set on the RabbitMQ message
rabbitmq.MESSAGE_ID
The message id to set on the RabbitMQ message
rabbitmq.DELIVERY_MODE
If the message should be persistent or not
rabbitmq.USERID
The userId to set on the RabbitMQ message
rabbitmq.CLUSTERID
The clusterId to set on the RabbitMQ message
rabbitmq.REPLY_TO
The replyTo to set on the RabbitMQ message
rabbitmq.CONTENT_ENCODING
The contentEncoding to set on the RabbitMQ message
rabbitmq.TYPE
The type to set on the RabbitMQ message
rabbitmq.EXPIRATION
The expiration to set on the RabbitMQ message
rabbitmq.TIMESTAMP
The timestamp to set on the RabbitMQ message
rabbitmq.APP_ID
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
[CONF] Apache Camel RabbitMQ
RabbitMQ
Page edited by Claus Ibsen
Changes (1)
...
| {{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. |
{div}
...
Full Content
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
groupIdorg.apache.camel/groupId
artifactIdcamel-rabbitmq/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
URI format
rabbitmq://hostname[:port]/exchangeName?[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
Property
Default
Description
autoAck
true
If messages should be auto acknowledged
autoDelete
true
If it is true, the message will be deleted when it is consumed
durable
true
If message is durable
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.
Headers
The following headers are set on exchanges when consuming messages.
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.
Property
Value
rabbitmq.ROUTING_KEY
The routing key that will be used when sending the message
rabbitmq.EXCHANGE_NAME
The exchange the message was received from, or sent to
rabbitmq.CONTENT_TYPE
The contentType to set on the RabbitMQ message
rabbitmq.PRIORITY
The priority header to set on the RabbitMQ message
rabbitmq.CORRELATIONID
The correlationId to set on the RabbitMQ message
rabbitmq.MESSAGE_ID
The message id to set on the RabbitMQ message
rabbitmq.DELIVERY_MODE
If the message should be persistent or not
rabbitmq.USERID
The userId to set on the RabbitMQ message
rabbitmq.CLUSTERID
The clusterId to set on the RabbitMQ message
rabbitmq.REPLY_TO
The replyTo to set on the RabbitMQ message
rabbitmq.CONTENT_ENCODING
The contentEncoding to set on the RabbitMQ message
rabbitmq.TYPE
The type to set on the RabbitMQ message
rabbitmq.EXPIRATION
The expiration to set on the RabbitMQ message
rabbitmq.TIMESTAMP
The timestamp to set on the RabbitMQ message
rabbitmq.APP_ID
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=BthreadPoolSize=1autoAck=false")
To send messages to an exchange called C
...to("rabbitmq://localhost/B")
See Also
Configuring Camel
Component
Endpoint
Getting Started
Stop
[CONF] Apache Camel RabbitMQ
RabbitMQ Page comment added by Dan Revel URI example should be rabbitmq://hostname:port/exchangeName?options Stop watching space | Change email notification preferences View Online | Reply To This
[CONF] Apache Camel RabbitMQ
RabbitMQ
Page edited by Christian Mueller
Changes (1)
...
{code}
rabbitmq:http://hostname[:port]/exchangeName?[options]
{code}
...
Full Content
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
groupIdorg.apache.camel/groupId
artifactIdcamel-rabbitmq/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
URI format
rabbitmq://hostname[:port]/exchangeName?[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
Property
Default
Description
autoAck
true
If messages should be auto acknowledged
autoDelete
true
If it is true, the message will be deleted when it is consumed
durable
true
If message is durable
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
Headers
The following headers are set on exchanges when consuming messages.
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.
Property
Value
rabbitmq.ROUTING_KEY
The routing key that will be used when sending the message
rabbitmq.EXCHANGE_NAME
The exchange the message was received from, or sent to
rabbitmq.CONTENT_TYPE
The contentType to set on the RabbitMQ message
rabbitmq.PRIORITY
The priority header to set on the RabbitMQ message
rabbitmq.CORRELATIONID
The correlationId to set on the RabbitMQ message
rabbitmq.MESSAGE_ID
The message id to set on the RabbitMQ message
rabbitmq.DELIVERY_MODE
If the message should be persistent or not
rabbitmq.USERID
The userId to set on the RabbitMQ message
rabbitmq.CLUSTERID
The clusterId to set on the RabbitMQ message
rabbitmq.REPLY_TO
The replyTo to set on the RabbitMQ message
rabbitmq.CONTENT_ENCODING
The contentEncoding to set on the RabbitMQ message
rabbitmq.TYPE
The type to set on the RabbitMQ message
rabbitmq.EXPIRATION
The expiration to set on the RabbitMQ message
rabbitmq.TIMESTAMP
The timestamp to set on the RabbitMQ message
rabbitmq.APP_ID
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=BthreadPoolSize=1autoAck=false")
To send messages to an exchange called C
...to("rabbitmq://localhost/B")
See Also
Configuring Camel
Component
Endpoint
Getting Started
Stop watching space
|
Change email notification preferences
View Online
|
View Changes
|
Add Comment
[CONF] Apache Camel RabbitMQ
RabbitMQ
Page edited by Robert Liguori
Changes (1)
...
{code}
rabbitmq:http://hostname[:port]/exchangeName?[options...]://name[?options] rabbitmq:http://hostname[:port]/exchangeName?[options]
{code}
...
Full Content
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
groupIdorg.apache.camel/groupId
artifactIdcamel-rabbitmq/artifactId
versionx.x.x/version
!-- use the same version as your Camel core version --
/dependency
URI format
rabbitmq:http://hostname[:port]/exchangeName?[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
Property
Default
Description
autoAck
true
If messages should be auto acknowledged
autoDelete
true
If it is true, the message will be deleted when it is consumed
durable
true
If message is durable
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
Headers
The following headers are set on exchanges when consuming messages.
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.
Property
Value
rabbitmq.ROUTING_KEY
The routing key that will be used when sending the message
rabbitmq.EXCHANGE_NAME
The exchange the message was received from, or sent to
rabbitmq.CONTENT_TYPE
The contentType to set on the RabbitMQ message
rabbitmq.PRIORITY
The priority header to set on the RabbitMQ message
rabbitmq.CORRELATIONID
The correlationId to set on the RabbitMQ message
rabbitmq.MESSAGE_ID
The message id to set on the RabbitMQ message
rabbitmq.DELIVERY_MODE
If the message should be persistent or not
rabbitmq.USERID
The userId to set on the RabbitMQ message
rabbitmq.CLUSTERID
The clusterId to set on the RabbitMQ message
rabbitmq.REPLY_TO
The replyTo to set on the RabbitMQ message
rabbitmq.CONTENT_ENCODING
The contentEncoding to set on the RabbitMQ message
rabbitmq.TYPE
The type to set on the RabbitMQ message
rabbitmq.EXPIRATION
The expiration to set on the RabbitMQ message
rabbitmq.TIMESTAMP
The timestamp to set on the RabbitMQ message
rabbitmq.APP_ID
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=BthreadPoolSize=1autoAck=false")
To send messages to an exchange called C
...to("rabbitmq://localhost/B")
See Also
Configuring Camel
Component
Endpoint
Getting Started
Stop watching space
|
Change email notification preferences
View Online
|
View Changes
[CONF] Apache Camel RabbitMQ
RabbitMQ
Page edited by willem jiang
Changes (1)
...
|| Property || Default || Description || | {{autoAck}} | {{true}} | If messages should be auto acknowledged |
| {{autoDelete}} | {{true}} | If it is true, the message will be deleted when it is consumed | | {{durable}} | {{true}} | If message is durable |
| {{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) |
...
Full Content
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
groupIdorg.apache.camel/groupId
artifactIdcamel-rabbitmq/artifactId
versionx.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
Property
Default
Description
autoAck
true
If messages should be auto acknowledged
autoDelete
true
If it is true, the message will be deleted when it is consumed
durable
true
If message is durable
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
Headers
The following headers are set on exchanges when consuming messages.
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.
Property
Value
rabbitmq.ROUTING_KEY
The routing key that will be used when sending the message
rabbitmq.EXCHANGE_NAME
The exchange the message was received from, or sent to
rabbitmq.CONTENT_TYPE
The contentType to set on the RabbitMQ message
rabbitmq.PRIORITY
The priority header to set on the RabbitMQ message
rabbitmq.CORRELATIONID
The correlationId to set on the RabbitMQ message
rabbitmq.MESSAGE_ID
The message id to set on the RabbitMQ message
rabbitmq.DELIVERY_MODE
If the message should be persistent or not
rabbitmq.USERID
The userId to set on the RabbitMQ message
rabbitmq.CLUSTERID
The clusterId to set on the RabbitMQ message
rabbitmq.REPLY_TO
The replyTo to set on the RabbitMQ message
rabbitmq.CONTENT_ENCODING
The contentEncoding to set on the RabbitMQ message
rabbitmq.TYPE
The type to set on the RabbitMQ message
rabbitmq.EXPIRATION
The expiration to set on the RabbitMQ message
rabbitmq.TIMESTAMP
The timestamp to set on the RabbitMQ message
rabbitmq.APP_ID
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.
[CONF] Apache Camel RabbitMQ
RabbitMQ
Page edited by stephen samuel
Changes (1)
...
*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 *amqpg:* component.
Maven users will need to add the following dependency to their {{pom.xml}} for this component:
...
Full Content
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
groupIdorg.apache.camel/groupId
artifactIdcamel-rabbitmq/artifactId
versionx.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
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.
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
Stop watching space
|
Change email notification preferences
View Online
|
View Changes
|
Add Comment
[CONF] Apache Camel RabbitMQ
RabbitMQ
Page edited by stephen samuel
Comment:
Added first set of documentation
Changes (1)
...
*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 *amqpg:* component. Maven users will need to add the following dependency to their {{pom.xml}} for this component: {code:xml} dependency groupIdorg.apache.camel/groupId artifactIdcamel-rabbitmq/artifactId versionx.x.x/version !-- use the same version as your Camel core version -- /dependency {code} h3. URI format {code} rabbitmq:http://hostname[:port]/exchangeName?[options...]://name[?options] {code} 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 h3. Options {div:class=confluenceTableSmall} || 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 | {div} h3. Headers The following headers are set on exchanges during message transport. {div:class=confluenceTableSmall} || 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}} | ) | {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. h3. 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. h3. Samples ... to be completed
Full Content
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 amqpg: component.
Maven users will need to add the following dependency to their pom.xml for this component:
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-rabbitmq/artifactId
versionx.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
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.
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
Stop watching
[CONF] Apache Camel RabbitMQ
RabbitMQ
Page edited by stephen samuel
Changes (14)
...
h3. Headers
The following headers are set on exchanges during message transport. when consuming messages.
{div:class=confluenceTableSmall} || Property || Value || | {{rabbitmq.ROUTING_KEY}} | | | {{rabbitmq.EXCHANGE_NAME}} | |
| {{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} || 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}} | ) |
{div}
...
Full Content
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
groupIdorg.apache.camel/groupId
artifactIdcamel-rabbitmq/artifactId
versionx.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
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 when consuming messages.
Property
Value
rabbitmq.ROUTING_KEY
rabbitmq.EXCHANGE_NAME
rabbitmq.DELIVERY_TAG
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.
Property
Value
rabbitmq.ROUTING_KEY
rabbitmq.EXCHANGE_NAME
rabbitmq.CONTENT_TYPE
rabbitmq.PRIORITY
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
Stop watching space
|
Change email notification preferences
View Online
|
View Changes
|
Add Comment
[CONF] Apache Camel RabbitMQ
RabbitMQ
Page edited by stephen samuel
Changes (6)
...
{div:class=confluenceTableSmall} || Property || Default || Description ||
| {{autoAck}} | {{true}} | If messages should be auto acknowledged |
| {{queue}} | {{random uuid}} | The queue to receive messages from |
| {{routingKey}} | {{null}} | The routing key to use when producing messages |
| {{threadPoolSize}} | {{10}} | |
| {{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 |
{div}
...
Full Content
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
groupIdorg.apache.camel/groupId
artifactIdcamel-rabbitmq/artifactId
versionx.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
Property
Default
Description
autoAck
true
If messages should be auto acknowledged
queue
random uuid
The queue to receive messages from
routingKey
null
The routing key to use when producing messages
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
Headers
The following headers are set on exchanges when consuming messages.
Property
Value
rabbitmq.ROUTING_KEY
rabbitmq.EXCHANGE_NAME
rabbitmq.DELIVERY_TAG
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.
Property
Value
rabbitmq.ROUTING_KEY
rabbitmq.EXCHANGE_NAME
rabbitmq.CONTENT_TYPE
rabbitmq.PRIORITY
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
Stop watching space
|
Change email notification preferences
View Online
|
View Changes
|
Add Comment
[CONF] Apache Camel RabbitMQ
RabbitMQ
Page edited by stephen samuel
Changes (4)
...
{code}
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
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.
h3. Options
...
| {{autoAck}} | {{true}} | If messages should be auto acknowledged | | {{queue}} | {{random uuid}} | The queue to receive messages from |
| {{routingKey}} | {{null}} | The routing key to use when producing messages |
| {{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 |
...
Full Content
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
groupIdorg.apache.camel/groupId
artifactIdcamel-rabbitmq/artifactId
versionx.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
Property
Default
Description
autoAck
true
If messages should be auto acknowledged
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
Headers
The following headers are set on exchanges when consuming messages.
Property
Value
rabbitmq.ROUTING_KEY
rabbitmq.EXCHANGE_NAME
rabbitmq.DELIVERY_TAG
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.
Property
Value
rabbitmq.ROUTING_KEY
rabbitmq.EXCHANGE_NAME
rabbitmq.CONTENT_TYPE
rabbitmq.PRIORITY
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
Stop watching space
|
Change email notification preferences
View Online
|
View Changes
|
Add Comment
[CONF] Apache Camel RabbitMQ
RabbitMQ
Page edited by stephen samuel
Comment:
added samples
Changes (2)
...
h3. Samples
... to be completed
To receive messages from a queue that is bound to an exchange A with the routing key B, {code} from(rabbitmq://localhost/A?routingKey=B) {code} To receive messages from a queue with a single thread with auto acknowledge disabled. {code} from(rabbitmq://localhost/A?routingKey=BthreadPoolSize=1autoAck=false) {code} To send messages to an exchange called C {code} ...to(rabbitmq://localhost/B) {code}
Full Content
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
groupIdorg.apache.camel/groupId
artifactIdcamel-rabbitmq/artifactId
versionx.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
Property
Default
Description
autoAck
true
If messages should be auto acknowledged
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
Headers
The following headers are set on exchanges when consuming messages.
Property
Value
rabbitmq.ROUTING_KEY
rabbitmq.EXCHANGE_NAME
rabbitmq.DELIVERY_TAG
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.
Property
Value
rabbitmq.ROUTING_KEY
rabbitmq.EXCHANGE_NAME
rabbitmq.CONTENT_TYPE
rabbitmq.PRIORITY
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 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=BthreadPoolSize=1autoAck=false")
To send messages to an exchange called C
...to("rabbitmq://localhost/B")
Stop watching space
|
Change email notification preferences
View Online
|
View Changes
|
Add Comment
[CONF] Apache Camel RabbitMQ
RabbitMQ
Page edited by stephen samuel
Changes (6)
...
{div:class=confluenceTableSmall} || Property || Value ||
| {{rabbitmq.ROUTING_KEY}} | | | {{rabbitmq.EXCHANGE_NAME}} | | | {{rabbitmq.DELIVERY_TAG}} | |
| {{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 |
{div}
...
{div:class=confluenceTableSmall} || Property || Value ||
| {{rabbitmq.ROUTING_KEY}} | The routing key that will be used when sending the message |
| {{rabbitmq.EXCHANGE_NAME}} | The exchange the message was received from, or sent to |
| {{rabbitmq.CONTENT_TYPE}} | | | {{rabbitmq.PRIORITY}} | | | {{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}} | |
| {{rabbitmq.CONTENT_TYPE}} | The contentType to set on the RabbitMQ message | | {{rabbitmq.PRIORITY}} | The priority header to set on the RabbitMQ message | | {{rabbitmq.CORRELATIONID}} | The correlationId to set on the RabbitMQ message | | {{rabbitmq.MESSAGE_ID}} | The message id to set on the RabbitMQ message | | {{rabbitmq.DELIVERY_MODE}} | If the message should be persistent or not | | {{rabbitmq.USERID}} | The userId to set on the RabbitMQ message | | {{rabbitmq.CLUSTERID}} | The clusterId to set on the RabbitMQ message | | {{rabbitmq.REPLY_TO}} | The replyTo to set on the RabbitMQ message | | {{rabbitmq.CONTENT_ENCODING}} | The contentEncoding to set on the RabbitMQ message | | {{rabbitmq.TYPE}} | The type to set on the RabbitMQ message| | {{rabbitmq.EXPIRATION}} | The expiration to set on the RabbitMQ message | | {{rabbitmq.TIMESTAMP}} | The timestamp to set on the RabbitMQ message | | {{rabbitmq.APP_ID}} | The appId to set on the RabbitMQ message |
{div}
...
Full Content
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
groupIdorg.apache.camel/groupId
artifactIdcamel-rabbitmq/artifactId
versionx.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
Property
Default
Description
autoAck
true
If messages should be auto acknowledged
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
Headers
The following headers are set on exchanges when consuming messages.
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.
Property
Value
rabbitmq.ROUTING_KEY
The routing key that will be used when sending the message
rabbitmq.EXCHANGE_NAME
The exchange the message was received from, or sent to
rabbitmq.CONTENT_TYPE
The contentType to set on the RabbitMQ message
rabbitmq.PRIORITY
The priority header to set
[CONF] Apache Camel RabbitMQ
RabbitMQ
Page edited by stephen samuel
Changes (1)
...
...to(rabbitmq://localhost/B) {code}
{include:Endpoint See Also}
Full Content
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
groupIdorg.apache.camel/groupId
artifactIdcamel-rabbitmq/artifactId
versionx.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
Property
Default
Description
autoAck
true
If messages should be auto acknowledged
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
Headers
The following headers are set on exchanges when consuming messages.
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.
Property
Value
rabbitmq.ROUTING_KEY
The routing key that will be used when sending the message
rabbitmq.EXCHANGE_NAME
The exchange the message was received from, or sent to
rabbitmq.CONTENT_TYPE
The contentType to set on the RabbitMQ message
rabbitmq.PRIORITY
The priority header to set on the RabbitMQ message
rabbitmq.CORRELATIONID
The correlationId to set on the RabbitMQ message
rabbitmq.MESSAGE_ID
The message id to set on the RabbitMQ message
rabbitmq.DELIVERY_MODE
If the message should be persistent or not
rabbitmq.USERID
The userId to set on the RabbitMQ message
rabbitmq.CLUSTERID
The clusterId to set on the RabbitMQ message
rabbitmq.REPLY_TO
The replyTo to set on the RabbitMQ message
rabbitmq.CONTENT_ENCODING
The contentEncoding to set on the RabbitMQ message
rabbitmq.TYPE
The type to set on the RabbitMQ message
rabbitmq.EXPIRATION
The expiration to set on the RabbitMQ message
rabbitmq.TIMESTAMP
The timestamp to set on the RabbitMQ message
rabbitmq.APP_ID
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=BthreadPoolSize=1autoAck=false")
To send messages to an exchange called C
...to("rabbitmq://localhost/B")
See Also
Configuring Camel
Component
Endpoint
Getting Started
Stop watching space
|
Change email notification preferences
View Online
|
View Changes
|
Add Comment
[CONF] Apache Camel RabbitMQ
RabbitMQ Page added by willem jiang Stop watching space | Change email notification preferences View Online | Add Comment
[CONF] Apache Camel RabbitMQ
RabbitMQ Page edited by willem jiang Changes (2) h2. RabbitMQ Component *Available as of Camel 2.12* Full Content RabbitMQ Component Available as of Camel 2.12 Stop watching space | Change email notification preferences View Online | View Changes | Add Comment
