Simple JMS Batch Component

Simple JMS Batch Component

Scheme: sjms-batch
Name Kind Type Required Deprecated Default Value Enum Values Description
destinationName path java.lang.String true false The destination name. Only queues are supported, names may be prefixed by 'queue:'.
consumerCount parameter int false 1 The number of JMS sessions to consume from
completionSize parameter int false 200 The number of messages consumed at which the batch will be completed
completionTimeout parameter int false 500 The timeout from receipt of the first first message when the batch will be completed
pollDuration parameter int false 1000 The duration in milliseconds of each poll for messages. completionTimeOut will be used if it is shorter and a batch has started.
aggregationStrategy parameter org.apache.camel.processor.aggregate.AggregationStrategy true false The aggregation strategy to use, which merges all the batched messages into a single message
headerFilterStrategy parameter org.apache.camel.spi.HeaderFilterStrategy false To use a custom HeaderFilterStrategy to filter header to and from Camel message.
includeAllJMSXProperties parameter boolean false 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.
allowNullBody parameter boolean false true 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 parameter boolean false true Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. See section about how mapping works below for more details.
messageCreatedStrategy parameter org.apache.camel.component.sjms.jms.MessageCreatedStrategy false 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 parameter org.apache.camel.component.sjms.jms.JmsKeyFormatStrategy false 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.
exchangePattern parameter org.apache.camel.ExchangePattern false InOnly InOnly
RobustInOnly
InOut
InOptionalOut
OutOnly
RobustOutOnly
OutIn
OutOptionalIn
Sets the default exchange pattern when creating an exchange
synchronous parameter boolean false false Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).

sjms-batch consumer