Option | Default Value | Description |
|---|
acknowledgementMode
| AUTO_ACKNOWLEDGE
| The JMS acknowledgement name, which is one of: TRANSACTED, AUTO_ACKNOWLEDGE or DUPS_OK_ACKNOWLEDGE. CLIENT_ACKNOWLEDGE is not supported at this time. |
consumerCount
| 1
| Defines the number of MessageListener instances. |
durableSubscriptionId
| null
| Required for a durable subscriptions. |
exchangePattern
| InOnly
| Sets the Consumers message exchange pattern. |
messageSelector
| null
| Sets the message selector. |
synchronous
| true
| Sets whether the Endpoint will use synchronous or asynchronous processing. |
transacted
| false
| If the endpoint should use a JMS Session transaction. |
transactionBatchCount
| 1
| The number of exchanges to process before committing a local JMS transaction. The transacted property must also be set to true or this property will be ignored. |
transactionBatchTimeout
| 5000
| The amount of time a the transaction will stay open between messages before committing what has already been consumed. Minimum value is 1000ms. |
ttl
| -1
| Disabled by default. Sets the Message time to live header. |
asyncStartListener | false | Whether to startup the consumer 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 | Whether to stop the consumer message listener asynchronously, when stopping a route. |
