Option | Default Value | Description |
|---|
acknowledgementMode
| AUTO_ACKNOWLEDGE
| The JMS acknowledgement name, which is one of: SESSION_TRANSACTED, AUTO_ACKNOWLEDGE or DUPS_OK_ACKNOWLEDGE. CLIENT_ACKNOWLEDGE is not supported at this time. |
consumerCount
| 1
| InOut only. Defines the number of MessageListener instances that for response consumers. |
exchangePattern
| InOnly
| Sets the Producers message exchange pattern. |
namedReplyTo
| null
| InOut only. Specifies a named reply to destination for responses. |
persistent
| true
| Whether a message should be delivered with persistence enabled. |
producerCount
| 1
| Defines the number of MessageProducer instances. |
responseTimeOut
| 5000
| InOut only. Specifies the amount of time an InOut Producer will wait for its response. |
synchronous
| true
| Sets whether the Endpoint will use synchronous or asynchronous processing. |
transacted
| false
| If the endpoint should use a JMS Session transaction. |
ttl
| -1
| Disabled by default. Sets the Message time to live header. |
prefillPool | true | Camel 2.14: Whether to prefill the producer connection pool on startup, or create connections lazy when needed. |
| allowNullBody | true | Camel 2.15.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. |
mapJmsMessage | true | Camel 2.16: Specifies whether Camel should auto map the received JMS message to an appropiate payload type, such as javax.jms.TextMessage to a String etc. |
messageCreatedStrategy | | Camel 2.16: To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message. |
| jmsKeyFormatStrategy | | Camel 2.16: 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 theorg.apache.camel.component.jms.JmsKeyFormatStrategy and refer to it using the # notation. |
| includeAllJMSXProperties | | Camel 2.16: 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. |
