camel-rabbitmq-kafka-connector source configuration

Required The exchange name determines the exchange to which the produced messages will be sent to. In the case of consumers, the exchange name determines the exchange the queue will be bound to.

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.

If it is true, the exchange will be deleted when it is no longer in use.

Enables connection automatic recovery (uses connection implementation that performs automatic recovery when existing connection has failures).

To use a custom RabbitMQ connection factory. When this option is set, all connection options (connectionTimeout, requestedChannelMax…​) set on URI are not used.

The name of the dead letter exchange.

The type of the dead letter exchange One of: [direct] [fanout] [headers] [topic].

Enum values:

The name of the dead letter queue.

The routing key for the dead letter exchange.

If the option is true, camel declare the exchange and queue name and bind them together. If the option is false, camel won’t declare the exchange and queue name on the server.

If we are declaring a durable exchange (the exchange will survive a server restart).

The exchange type such as direct or topic. One of: [direct] [fanout] [headers] [topic].

Enum values:

Exclusive queues may only be accessed by the current connection, and are deleted when that connection closes.

The hostname of the running rabbitmq instance or cluster.

Passive queues depend on the queue already to be available at RabbitMQ.

Port number for the host with the running rabbitmq instance or cluster. Default value is 5672.

The queue to receive messages from.

The routing key to use when binding a consumer queue to the exchange. For producer routing keys, you set the header rabbitmq.ROUTING_KEY.

If true the producer will not declare and bind a dead letter queue. This can be used if you have also DLQ rabbitmq consumer and you want to avoid argument clashing between Producer and Consumer. This option have no effect, if DLQ configured (deadLetterExchange option is not set).

This can be used if we need to declare the queue but not the exchange.

If true the queue will not be bound to the exchange after declaring it.

If true the producer will not declare and bind a queue. This can be used for directing messages via an existing routing key.

The vhost for the channel.

If messages should be auto acknowledged.

Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.

Number of concurrent consumers when consuming from broker. (eg similar as to the same option for the JMS component).

Specify a client-generated consumer tag to establish context when invoking the consume operation.

Request exclusive access to the queue (meaning only this consumer can access the queue). This is useful when you want a long-lived shared queue to be temporarily accessible by just one consumer.

The maximum number of messages that the server will deliver, 0 if unlimited. You need to specify the option of prefetchSize, prefetchCount, prefetchGlobal at the same time.

Enables the quality of service on the RabbitMQConsumer side. You need to specify the option of prefetchSize, prefetchCount, prefetchGlobal at the same time.

If the settings should be applied to the entire channel rather than each consumer You need to specify the option of prefetchSize, prefetchCount, prefetchGlobal at the same time.

The maximum amount of content (measured in octets) that the server will deliver, 0 if unlimited. You need to specify the option of prefetchSize, prefetchCount, prefetchGlobal at the same time.

Decides whether an exception during declaration of exchanges or queues is recoverable or not. If the option is false, camel will throw an exception when starting the consumer, which will interrupt application startup (e.g. in the case when the exchange / queue is already declared in RabbitMQ and has incompatible configuration). If set to true, the consumer will try to reconnect periodically.

This is used by the consumer to control rejection of the message. When the consumer is complete processing the exchange, and if the exchange failed, then the consumer is going to reject the message from the RabbitMQ broker. If the header CamelRabbitmqRequeue is present then the value of the header will be used, otherwise this endpoint value is used as fallback. If the value is false (by default) then the message is discarded/dead-lettered. If the value is true, then the message is re-queued.

To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.

Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut].

Enum values:

The consumer uses a Thread Pool Executor with a fixed number of threads. This setting allows you to set that number of threads.

Whether to allow Java serialization of the message body or not. If this value is true, the message body will be serialized on the producer side using Java serialization, if no type converter can handle the message body. On the consumer side, it will deserialize the message body if this value is true and the message contains a CamelSerialize header. Setting this value to true may introduce a security vulnerability as it allows an attacker to attempt to deserialize to a gadget object which could result in a RCE or other security vulnerability.

Specify arguments for configuring the different RabbitMQ concepts, a different prefix is required for each: Exchange: arg.exchange. Queue: arg.queue. Binding: arg.binding. DLQ: arg.dlq.queue. DLQ binding: arg.dlq.binding. For example to declare a queue with message ttl argument: http://localhost:5672/exchange/queueargs=arg.queue.x-message-ttl=60000.

Connection client properties (client info used in negotiating with the server).

Custom rabbitmq ExceptionHandler for ConnectionFactory.

Connection timeout.

Network recovery interval in milliseconds (interval used when recovering from network failure).

Connection requested channel max (max number of channels offered).

Connection requested frame max (max size of frame offered).

Connection requested heartbeat (heart-beat in seconds offered).

Set timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds).

Set requestTimeoutCheckerInterval for inOut exchange.

Enables connection topology recovery (should topology recovery be performed).

When true and an inOut Exchange failed on the consumer side send the caused Exception back in the response.

Password for authenticated access.

Enables SSL on connection, accepted value are true, TLS and 'SSLv3.

Configure SSL trust manager, SSL should be enabled for this option to be effective.

Username in case of authenticated access.

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.

If it is true, the exchange will be deleted when it is no longer in use.

To use a custom RabbitMQ connection factory. When this option is set, all connection options (connectionTimeout, requestedChannelMax…​) set on URI are not used.

The name of the dead letter exchange.

The type of the dead letter exchange One of: [direct] [fanout] [headers] [topic].

Enum values:

The name of the dead letter queue.

The routing key for the dead letter exchange.

If the option is true, camel declare the exchange and queue name and bind them together. If the option is false, camel won’t declare the exchange and queue name on the server.

If we are declaring a durable exchange (the exchange will survive a server restart).

Exclusive queues may only be accessed by the current connection, and are deleted when that connection closes.

The hostname of the running RabbitMQ instance or cluster.

Passive queues depend on the queue already to be available at RabbitMQ.

Port number for the host with the running rabbitmq instance or cluster.

This can be used if we need to declare the queue but not the exchange.

If true the queue will not be bound to the exchange after declaring it.

If true the producer will not declare and bind a queue. This can be used for directing messages via an existing routing key.

The vhost for the channel.

If messages should be auto acknowledged.

Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.

Request exclusive access to the queue (meaning only this consumer can access the queue). This is useful when you want a long-lived shared queue to be temporarily accessible by just one consumer.

The maximum number of messages that the server will deliver, 0 if unlimited. You need to specify the option of prefetchSize, prefetchCount, prefetchGlobal at the same time.

Enables the quality of service on the RabbitMQConsumer side. You need to specify the option of prefetchSize, prefetchCount, prefetchGlobal at the same time.

If the settings should be applied to the entire channel rather than each consumer You need to specify the option of prefetchSize, prefetchCount, prefetchGlobal at the same time.

The maximum amount of content (measured in octets) that the server will deliver, 0 if unlimited. You need to specify the option of prefetchSize, prefetchCount, prefetchGlobal at the same time.

Decides whether an exception during declaration of exchanges or queues is recoverable or not. If the option is false, camel will throw an exception when starting the consumer, which will interrupt application startup (e.g. in the case when the exchange / queue is already declared in RabbitMQ and has incompatible configuration). If set to true, the consumer will try to reconnect periodically.

The consumer uses a Thread Pool Executor with a fixed number of threads. This setting allows you to set that number of threads.

Specify arguments for configuring the different RabbitMQ concepts, a different prefix is required for each: Exchange: arg.exchange. Queue: arg.queue. Binding: arg.binding. DLQ: arg.dlq.queue. DLQ Binding: arg.dlq.binding. For example to declare a queue with message ttl argument: http://localhost:5672/exchange/queueargs=arg.queue.x-message-ttl=60000.

Whether to auto-detect looking up RabbitMQ connection factory from the registry. When enabled and a single instance of the connection factory is found then it will be used. An explicit connection factory can be configured on the component or endpoint level which takes precedence.

Enables connection automatic recovery (uses connection implementation that performs automatic recovery when connection shutdown is not initiated by the application).

Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.

Connection client properties (client info used in negotiating with the server).

Custom rabbitmq ExceptionHandler for ConnectionFactory.

Connection timeout.

Network recovery interval in milliseconds (interval used when recovering from network failure).

Connection requested channel max (max number of channels offered).

Connection requested frame max (max size of frame offered).

Connection requested heartbeat (heart-beat in seconds offered).

Set timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds).

Set requestTimeoutCheckerInterval for inOut exchange.

Enables connection topology recovery (should topology recovery be performed).

When true and an inOut Exchange failed on the consumer side send the caused Exception back in the response.

Password for authenticated access.

Enables SSL on connection, accepted value are true, TLS and 'SSLv3.

Configure SSL trust manager, SSL should be enabled for this option to be effective.

Username in case of authenticated access.