Option	Default Value	Description
`acceptMessagesWhileStopping`	`false`	Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqued on the queue. If this option is `false`, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead lett er queue on the JMS broker. To avoid this its recommended to enable this option.
`acknowledgementModeName`	`AUTO_ACKNOWLEDGE`	The JMS acknowledgement name, which is one of: `SESSION_TRANSACTED`, `CLIENT_ACKNOWLEDGE`, `AUTO_ACKNOWLEDGE`, `DUPS_OK_ACKNOWLEDGE`
`acknowledgementMode`	`-1`	The JMS acknowledgement mode defined as an Integer. Allows you to set vendor-specific extensions to the acknowledgment mode. For the regular modes, it is preferable to use the `acknowledgementModeName` instead.
`allowNullBody`	`true`	Camel 2.9.3/2.10.1: Whether to allow sending messages with no body. If this option is `false` and the message body is null, then an `JMSException` is thrown.
`alwaysCopyMessage`	`false`	If `true`, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a `replyToDestinationSelectorName` is set (incidentally, Camel will set the `alwaysCopyMessage` option to `true`, if a `replyToDestinationSelectorName` is set)
`asyncConsumer`	`false`	Camel 2.9: Whether the `JmsConsumer` processes the Exchange asynchronously. If enabled then the `JmsConsumer` may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the `JmsConsumer` will pickup the next message from the JMS queue. Note if `transacted` has been enabled, then `asyncConsumer=true` does not run a synchronously, as transactions must be executed synchronously (Camel 3.0 may support async transactions).
`asyncStartListener`	`false`	Camel 2.10: Whether to startup the `JmsConsumer` message listener asynchronously, when starting a route. For example if a `JmsConsumer` cannot get a connection to a remote JMS broker, then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to `true`, you will let routes startup, while the `JmsConsumer` connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is used, then beware that if the connection could not be established, then an exception is logged at `WARN` level, and the consumer will not be able to receive messages ; You can then restart the route to retry.
`asyncStopListener`	`false`	Camel 2.10: Whether to stop the `JmsConsumer` message listener asynchronously, when stopping a route.
`autoStartup`	`true`	Specifies whether the consumer container should auto-startup.
`cacheLevelName`	CACHE_AUTO (Camel >= 2.8.0) - CACHE_CONSUMER (Camel <= 2.7.1)	Sets the cache level by name for the underlying JMS resources. Possible values are: `CACHE_AUTO`, `CACHE_CONNECTION`, `CACHE_CONSUMER`, `CACHE_NONE`, and `CACHE_SESSION`. The default setting for Camel 2.8 and newer is `CACHE_AUTO`. For Camel 2.7.1 and older the default is `CACHE_CONSUMER`. See the Spring documentation and Transactions Cache Levels for more information.
`cacheLevel`		Sets the cache le vel by ID for the underlying JMS resources. See `cacheLevelName` option for more details.
`consumerType`	`Default`	The consumer type to use, which can be one of: `Simple`, `Default`, or `Custom`. The consumer type determines which Spring JMS listener to use. `Default` will use `org.springframework.jms.listener.DefaultMessageListenerContainer`, `Simple` will use `org.springframework.jms.listener.SimpleMessageListenerContainer`. When `Custom` is specified, the `MessageListenerContainerFactory` defined by the `messageListenerContainerFactoryRef` option will determine what `org.springframework.jms.listener.AbstractMessageListenerContainer` to use (new option in Camel 2.10.2 onwards). This option was temporary rem oved in Camel 2.7 and 2.8. But has been added back from Camel 2.9 onwards.
`connectionFactory`	`null`	The default JMS connection factory to use for the `listenerConnectionFactory` and `templateConnectionFactory`, if neither is specified.
`defaultTaskExecutorType`	(see description)	Camel 2.10.4: Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: `SimpleAsync` (uses Spring's SimpleAsyncTaskExecutor) or `ThreadPool` (uses Spring's ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints and SimpleAsync for reply consumers. The use of `ThreadPool` is recommended to reduce "thread trash" in elastic configurations with dynamically increasing and decreasing concurrent consumers.
`deliveryPersistent`	`true`	Specifies whether persistent delivery is used by defau lt.
`destination`	`null`	Specifies the JMS Destination object to use on this endpoint.
`destinationName`	`null`	Specifies the JMS destination name to use on this endpoint.
`destinationResolver`	`null`	A pluggable `org.springframework.jms.support.destination.DestinationResolver` that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry).
`disableTimeToLive`	`false`	Camel 2.8: Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the `requestTimeout` value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use `disableTimeToLive=true` to not set a time to live value on the sent message. Then the message will not expire on the receiver system. See below in section About time to live for more details.
`eagerLoadingOfProperties`	`false`	Enables eager loading of JMS properties as soon as a message is received, which is generally inefficient, because the JMS properties might not be required. But this feature can sometimes catch early any issues with the underlying JMS provider and the use of JMS properties. This feature can also be used for testing purposes, to ensure JMS properties can be understood and handled correctly.
`exceptionListener`	`null`	Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.
`errorHandler`	`null`	Camel 2.8.2, 2.9: Specifies a `org.springframework.util.ErrorHandler` to be invoked in case of any uncaught exceptions thrown while processing a `Message`. By default these exceptions will be logged at the WARN level, if no `errorHandler` has been configured. From Camel 2.9.1: onwards you can configure logging level and whether stack traces should be logged using the below two options. This makes it much easier to configure, than having to code a custom `errorHandler`.
`errorHandlerLoggingLevel`	`WARN`	Camel 2.9.1: Allows to configure the default `errorHandler` logging level for logging uncaught exceptions.
`errorHandlerLogStackTrace`	`true`	Camel 2.9.1: Allows to control whether stacktraces should be logged or not, by the default `errorHandler`.
`explicitQosEnabled`	`false`	Set if the `deliveryMode`, `priority` or `timeToLive` qualities of service should be used when sending messages. This option is based on Spring's `JmsTemplate`. The `deliveryMode`, `priority` and `timeToLive` options are applied to the current endpoint. This contrasts with the `preserveMessageQos` option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers.
`exposeListenerSession`	`true`	Specifies whether the listener session should be exposed when consuming messages.
`forceSendOriginalMessage`	`false`	Camel 2.7: When using `mapJmsMessage=false` Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to `true` to force Camel to send the original JMS message that was received.
`idleTaskExecutionLimit`	`1`	Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the `maxConcurrentConsumers` setting). There is additional doc available from Spring.
`idleConsumerLimit`	`1`	Camel 2.8.2, 2.9: Specify the limit for the number of consumers that are allowed to be idle at any given time.
`includeSentJMSMessageID`	`false`	Camel 2.10.3: Only applic able when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination.
`jmsMessageType`	`null`	Allows you to force the use of a specific `javax.jms.Message` implementation for sending JMS messages. Possible values are: `Bytes`, `Map`, `Object`, `Stream`, `Text`. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it.
`jmsKeyFormatStrategy`	`defa ult`	Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: `default` and `passthrough`. The `default` strategy will safely marshal dots and hyphens (`.` and `-`). The `passthrough` strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the `org.apache.camel.component.jms.JmsKeyFormatStrategy` and refer to it using the `#` notation.
`jmsOperations`	`null`	Allows you to use your own implementation of the `org.springframework.jms.core.JmsOperations` interface. Came l uses `JmsTemplate` as default. Can be used for testing purpose, but not used much as stated in the spring API docs.
`lazyCreateTransactionManager`	`true`	If `true`, Camel will create a `JmsTransactionManager`, if there is no `transactionManager` injected when option `transacted=true`.
`listenerConnectionFactory`	`null`	The JMS connection factory used for consuming messages.
`mapJmsMessage`	`true`	Specifies whether Camel should auto map the received JMS message to an appropiate payload type, such as `javax.jms.TextMessage` to a `String` etc. See section about how mapping works below for more details.
`maximumBrowseSize`	`-1`	Limits the number of messages fetched at most, when browsing endpoints using Browse or JMX API.
`messageConverter`	`null`	To use a custom Spring `org.springframework.jms.support.converter.MessageConverter` so you can be 100% in control how to map to/from a `javax.jms.Message`.
`messageIdEnabled`	`true`	When sending, specifies whether message IDs should be added.
`messageListenerContainerFactoryRef`	`null`	Camel 2.10.2: Registry ID of the `MessageListenerContainerFactory` used to determine what `org.springframework.jms.listener.AbstractMessageListenerContainer` to use to consume messages. Setting this will automatically set `consumerType` to `Custom`.
`messageTimestampEnabled`	`true`	Specifies whether timestamps should be enabled by default on sending messages.
`password`	`null`	The password for the connector factory.
`priority`	`4`	Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The `explicitQosEnabled` option must also be enabled in order for this option to have any effect.
`pubSubNoLocal`	`false`	Specifies whether to inhibit the de livery of messages published by its own connection.
`receiveTimeout`	None	The timeout for receiving messages (in milliseconds).
`recoveryInterval`	`5000`	Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds.
`replyToCacheLevelName`	CACHE_CONSUMER	Camel 2.9.1: Sets the cache level by name for the reply consumer when doing request/ reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: `CACHE_CONSUMER` for exclusive or shared w/ `replyToSelectorName`. And `CACHE_SESSION` for shared without `replyToSelectorName`. Some JMS brokers such as IBM WebSphere may require to set the `replyToCacheLevelName=CACHE_NONE` to work. Note: If using temporary queues then `CACHE_NONE` is not allowed, and you must use a higher value such as `CACHE_CONSUMER` or `CACHE_SESSION`.
`replyToDestinationSelectorName`	`null`	Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue).
`replyToDeliveryPersistent`	`true`	Specifies whether to use persistent delivery by default for replies.
`requestTimeoutCheckerInterval`	`1000`	Camel 2.9.2: Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS.By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout.
`subscriptionDurable`	`false`	@deprecated: Enabled by default, if you specify a `durableSubscriberName` and a `clientId`.
`taskExecutor`	`null`	Allows you to specify a custom task executor for consuming messages.
`taskExecutorSpring2`	`null`	Camel 2.6: To use when using Spring 2.x with Camel. Allows you to specify a custom task executor for consuming messages.
`templateConnectionFactory`	`null`	The JMS connection factory used for sending messages.
`transactedInOut`	`false`	@deprecated: Specifies whether to use transacted mode for sending messages using the InOut Exchange Pattern. Applies only to producer endpoints. See section Enabling Transacted Consumption for more details.
`transactionManager`	`null`	The Spring transaction manager to use.
`transactionName`	`"JmsConsumer[destinationName]"`	The name of the transaction to use.
`transactionTimeout`	`null`	The timeout value of the transaction (in seconds), if using transacted mode.
`transferException`	`false`	If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused `Excepti on` will be send back in response as a `javax.jms.ObjectMessage`. If the client is Camel, the returned `Exception` is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option takes precedence. The caught exception is required to be serializable. The original `Exception` on the consumer side can be wrapped in an outer exception such as `org.apache.camel.RuntimeCamelException` when returned to the producer.
`transferExchange`	`false`	You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, F ault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at `WARN` level. You must enable this option on both the producer and consumer side, so Camel knows the payloads is an Exchange and not a regular payload.
`username`	`null`	The username for the connector factory.
`useMessageIDAsCorrelationID`	`false`	Specifies whether `JMSMessageID` should always be used as `JMSCorrelationID` for InOut messages.
`useVersion102`	`false`	@deprecated (removed from Camel 2.5 onwards): Specifies whether the old JMS API should be used.

+ CACHE_CONSUMER (Camel <= 2.7.1) Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO, CACHE_CONNECTION, CACHE_CONSUMER, CACHE_NONE, and CACHE_SESSION. The default setting for Camel 2.8 and newer is CACHE_AUTO. For Camel 2.7.1 and older the default is CACHE_CONSUMER. See the Spring documentation and Transactions Cache Levels for more information. cacheLevel Sets the cache le vel by ID for the underlying JMS resources. See cacheLevelName option for more details. consumerType Default The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactoryRef option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use (new option in Camel 2.10.2 onwards). This option was temporary rem oved in Camel 2.7 and 2.8. But has been added back from Camel 2.9 onwards. connectionFactory null The default JMS connection factory to use for the listenerConnectionFactory and templateConnectionFactory, if neither is specified. defaultTaskExecutorType (see description) Camel 2.10.4: Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints and SimpleAsync for reply consumers. The use of ThreadPool is recommended to reduce "thread trash" in elastic configurations with dynamically increasing and decreasing concurrent consumers. deliveryPersistent true Specifies whether persistent delivery is used by defau lt. destination null Specifies the JMS Destination object to use on this endpoint. destinationName null Specifies the JMS destination name to use on this endpoint. destinationResolver null A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry). disableTimeToLive false Camel 2.8: Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive=true to not set a time to live value on the sent message. Then the message will not expire on the receiver system. See below in section About time to live for more details. eagerLoadingOfProperties false Enables eager loading of JMS properties as soon as a message is received, which is generally inefficient, because the JMS properties might not be required. But this feature can sometimes catch early any issues with the underlying JMS provider and the use of JMS properties. This feature can also be used for testing purposes, to ensure JMS properties can be understood and handled correctly. exceptionListener null Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. errorHandler null Camel 2.8.2, 2.9: Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. From Camel 2.9.1: onwards you can configure logging level and whether stack traces should be logged using the below two options. This makes it much easier to configure, than having to code a custom errorHandler. errorHandlerLoggingLevel WARN Camel 2.9.1: Allows to configure the default errorHandler logging level for logging uncaught exceptions. errorHandlerLogStackTrace true Camel 2.9.1: Allows to control whether stacktraces should be logged or not, by the default errorHandler. explicitQosEnabled false Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers. exposeListenerSession true Specifies whether the listener session should be exposed when consuming messages. forceSendOriginalMessage false Camel 2.7: When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received. idleTaskExecutionLimit 1 Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring. idleConsumerLimit 1 Camel 2.8.2, 2.9: Specify the limit for the number of consumers that are allowed to be idle at any given time. includeSentJMSMessageID false Camel 2.10.3: Only applic able when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination. includeAllJMSXProperties false Camel 2.11.2/2.12: Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply. jmsMessageType null Allows you to force the use of a specific javax.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it. jmsKeyFormatStrategy default Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the org.apache.camel.component.jms.JmsKeyFormatStrategy and refer to it using the # notation. jmsOperations null Allows you to use your own implementation of the org.springframework.jms.core.JmsOperations interface. Camel uses JmsTemplate as default. Can be used for testing purpose, but not used much as stated in the spring API docs. lazyCreateTransactionManager true If true, Camel will create a JmsTransactionManager, if there is no transactionMa nager injected when option transacted=true. listenerConnectionFactory null The JMS connection factory used for consuming messages. mapJmsMessage true Specifies whether Camel should auto map the received JMS message to an appropiate payload type, such as javax.jms.TextMessage to a String etc. See section about how mapping works below for more details. maximumBrowseSize -1 Limits the numb er of messages fetched at most, when browsing endpoints using Browse or JMX API. messageConverter null To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be 100% in control how to map to/from a javax.jms.Message. messageIdEnabled true When sending, specifies whether message IDs should be added. messageListenerContainerFactoryRef null Camel 2.10.2: Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom. messageTimestampEnabled true Specifies whether timestamps should be enabled by default on sending messages. password null The password for the connector factory. priority 4 Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect. pubSubNoLocal false Specifies whether to inhibit the delivery of messages published by its own connection. receiveTimeout None The timeout for receiving messages (in milliseconds). recoveryInterval 5000 Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds. replyToCacheLevelName CACHE_CONSUMER Camel 2.9.1: Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE_NONE to work. Note: If using temporary queues then CACHE_NONE is n ot allowed, and you must use a higher value such as CACHE_CONSUMER or CACHE_SESSION. replyToDestinationSelectorName null Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue). replyToDeliveryPersistent true Specifies whether to use persistent delivery by default for replies. requestTimeoutCheckerInterval 1000 Camel 2.9.2: Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS.By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout. subscriptionDurable false @deprecated: Enabled by default, if you specify a durableSubscriberName and a clientId. taskExecutor null Allows you to spe cify a custom task executor for consuming messages. taskExecutorSpring2 null Camel 2.6: To use when using Spring 2.x with Camel. Allows you to specify a custom task executor for consuming messages. templateConnectionFactory null The JMS connection factory used for sending messages. transactedInOut false @deprecated: Specifies whether to use transacted mode for sending messages using the InOut Exchange Pattern. Applies only to producer endpoints. See section Enabling Transacted Consumption for more details. transactionManager null The Spring transaction manager to use. transactionName "JmsConsumer[destinationName]" The name of the transaction to use. transactionTimeout null The time out value of the transaction (in seconds), if using transacted mode. transferException false If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option takes precedence. The caught exception is required to be se rializable. The original Exception on the consumer side can be wrapped in an outer exception such as org.apache.camel.RuntimeCamelException when returned to the producer. transferExchange false You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the payloads is an Exchange and not a regular payload. username null The username for the connector factory. useMessageIDAsCorrelationID false Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. useVersion102 false @deprecated (removed from Camel 2.5 onwards): Specifies whether the old JMS API should be used.