Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
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 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

Code Block
xml
xml
<bean id="customConnectionFactory" class="com.rabbitmq.client.ConnectionFactory">
<property name="host" value="localhost"/>
<property name="port" value="5672"/>
<property name="username" value="camel"/>
<property name="password" value="bugsbunny"/>
</bean>
<camelContext>
<route>
<from uri="direct:rabbitMQEx2"/>
<to uri="rabbitmq://localhost:5672/ex2?connectionFactory=#customConnectionFactory"/>
</route>
</camelContext>


Headers

The following headers are set on exchanges when consuming messages.

...