anchor.diff:  | idleConsumerLimit | int | Specify the limit for the number of consumers that are allowed to be idle at any given time.
   | maxConcurrentConsumers | int | Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.
   | replyToMaxConcurrentConsumers | int | Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.
  +| replyOnTimeoutToMaxConcurrentConsumers | int | Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS.
   | maxMessagesPerTask | int | The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max) then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required.
   | messageConverter | MessageConverter | To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message.
   | mapJmsMessage | boolean | 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.
  
positive.code: 
  
  
  [[JMS-MessageMappingbetweenJMSandCamel]]
  Message Mapping between JMS and Camel
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  
negative.code: 
  
  
  
  // endpoint options: START
  The JMS component supports 79 endpoint options which are listed below:
  
  {% raw %}
  [width="100%",cols="2s,1,1m,1m,5",options="header"]
  