Interface ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder

All Superinterfaces:
org.apache.camel.builder.EndpointProducerBuilder, org.apache.camel.EndpointProducerResolver
All Known Subinterfaces:
ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointBuilder
Enclosing interface:
ActiveMQ6EndpointBuilderFactory

public static interface ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder extends org.apache.camel.builder.EndpointProducerBuilder
Advanced builder for endpoint producers for the ActiveMQ 6.x component.
  • Method Details

    • basic

    • allowAdditionalHeaders

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder allowAdditionalHeaders(String allowAdditionalHeaders)
      This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example, some message systems, such as WMQ, do this with header names using prefix JMS_IBM_MQMD_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching. The option is a: java.lang.String type. Group: producer (advanced)
      Parameters:
      allowAdditionalHeaders - the value to set
      Returns:
      the dsl builder
    • allowNullBody

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder allowNullBody(boolean allowNullBody)
      Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown. The option is a: boolean type. Default: true Group: producer (advanced)
      Parameters:
      allowNullBody - the value to set
      Returns:
      the dsl builder
    • allowNullBody

      Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown. The option will be converted to a boolean type. Default: true Group: producer (advanced)
      Parameters:
      allowNullBody - the value to set
      Returns:
      the dsl builder
    • alwaysCopyMessage

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder alwaysCopyMessage(boolean alwaysCopyMessage)
      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). The option is a: boolean type. Default: false Group: producer (advanced)
      Parameters:
      alwaysCopyMessage - the value to set
      Returns:
      the dsl builder
    • alwaysCopyMessage

      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). The option will be converted to a boolean type. Default: false Group: producer (advanced)
      Parameters:
      alwaysCopyMessage - the value to set
      Returns:
      the dsl builder
    • correlationProperty

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder correlationProperty(String correlationProperty)
      When using InOut exchange pattern use this JMS property instead of JMSCorrelationID JMS property to correlate messages. If set messages will be correlated solely on the value of this property JMSCorrelationID property will be ignored and not set by Camel. The option is a: java.lang.String type. Group: producer (advanced)
      Parameters:
      correlationProperty - the value to set
      Returns:
      the dsl builder
    • disableTimeToLive

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder disableTimeToLive(boolean disableTimeToLive)
      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. The option is a: boolean type. Default: false Group: producer (advanced)
      Parameters:
      disableTimeToLive - the value to set
      Returns:
      the dsl builder
    • disableTimeToLive

      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. The option will be converted to a boolean type. Default: false Group: producer (advanced)
      Parameters:
      disableTimeToLive - the value to set
      Returns:
      the dsl builder
    • forceSendOriginalMessage

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder forceSendOriginalMessage(boolean forceSendOriginalMessage)
      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. The option is a: boolean type. Default: false Group: producer (advanced)
      Parameters:
      forceSendOriginalMessage - the value to set
      Returns:
      the dsl builder
    • forceSendOriginalMessage

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder forceSendOriginalMessage(String forceSendOriginalMessage)
      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. The option will be converted to a boolean type. Default: false Group: producer (advanced)
      Parameters:
      forceSendOriginalMessage - the value to set
      Returns:
      the dsl builder
    • includeSentJMSMessageID

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder includeSentJMSMessageID(boolean includeSentJMSMessageID)
      Only applicable 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. The option is a: boolean type. Default: false Group: producer (advanced)
      Parameters:
      includeSentJMSMessageID - the value to set
      Returns:
      the dsl builder
    • includeSentJMSMessageID

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder includeSentJMSMessageID(String includeSentJMSMessageID)
      Only applicable 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. The option will be converted to a boolean type. Default: false Group: producer (advanced)
      Parameters:
      includeSentJMSMessageID - the value to set
      Returns:
      the dsl builder
    • lazyStartProducer

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder lazyStartProducer(boolean lazyStartProducer)
      Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. The option is a: boolean type. Default: false Group: producer (advanced)
      Parameters:
      lazyStartProducer - the value to set
      Returns:
      the dsl builder
    • lazyStartProducer

      Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. The option will be converted to a boolean type. Default: false Group: producer (advanced)
      Parameters:
      lazyStartProducer - the value to set
      Returns:
      the dsl builder
    • replyToCacheLevelName

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder replyToCacheLevelName(String replyToCacheLevelName)
      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. The option is a: java.lang.String type. Group: producer (advanced)
      Parameters:
      replyToCacheLevelName - the value to set
      Returns:
      the dsl builder
    • replyToDestinationSelectorName

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder replyToDestinationSelectorName(String replyToDestinationSelectorName)
      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). The option is a: java.lang.String type. Group: producer (advanced)
      Parameters:
      replyToDestinationSelectorName - the value to set
      Returns:
      the dsl builder
    • streamMessageTypeEnabled

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder streamMessageTypeEnabled(boolean streamMessageTypeEnabled)
      Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMessage until no more data. The option is a: boolean type. Default: false Group: producer (advanced)
      Parameters:
      streamMessageTypeEnabled - the value to set
      Returns:
      the dsl builder
    • streamMessageTypeEnabled

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder streamMessageTypeEnabled(String streamMessageTypeEnabled)
      Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMessage until no more data. The option will be converted to a boolean type. Default: false Group: producer (advanced)
      Parameters:
      streamMessageTypeEnabled - the value to set
      Returns:
      the dsl builder
    • allowSerializedHeaders

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder allowSerializedHeaders(boolean allowSerializedHeaders)
      Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. The option is a: boolean type. Default: false Group: advanced
      Parameters:
      allowSerializedHeaders - the value to set
      Returns:
      the dsl builder
    • allowSerializedHeaders

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder allowSerializedHeaders(String allowSerializedHeaders)
      Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. The option will be converted to a boolean type. Default: false Group: advanced
      Parameters:
      allowSerializedHeaders - the value to set
      Returns:
      the dsl builder
    • artemisStreamingEnabled

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder artemisStreamingEnabled(boolean artemisStreamingEnabled)
      Whether optimizing for Apache Artemis streaming mode. This can reduce memory overhead when using Artemis with JMS StreamMessage types. This option must only be enabled if Apache Artemis is being used. The option is a: boolean type. Default: false Group: advanced
      Parameters:
      artemisStreamingEnabled - the value to set
      Returns:
      the dsl builder
    • artemisStreamingEnabled

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder artemisStreamingEnabled(String artemisStreamingEnabled)
      Whether optimizing for Apache Artemis streaming mode. This can reduce memory overhead when using Artemis with JMS StreamMessage types. This option must only be enabled if Apache Artemis is being used. The option will be converted to a boolean type. Default: false Group: advanced
      Parameters:
      artemisStreamingEnabled - the value to set
      Returns:
      the dsl builder
    • asyncStartListener

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder asyncStartListener(boolean asyncStartListener)
      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 fail-over. 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. The option is a: boolean type. Default: false Group: advanced
      Parameters:
      asyncStartListener - the value to set
      Returns:
      the dsl builder
    • asyncStartListener

      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 fail-over. 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. The option will be converted to a boolean type. Default: false Group: advanced
      Parameters:
      asyncStartListener - the value to set
      Returns:
      the dsl builder
    • asyncStopListener

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder asyncStopListener(boolean asyncStopListener)
      Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. The option is a: boolean type. Default: false Group: advanced
      Parameters:
      asyncStopListener - the value to set
      Returns:
      the dsl builder
    • asyncStopListener

      Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. The option will be converted to a boolean type. Default: false Group: advanced
      Parameters:
      asyncStopListener - the value to set
      Returns:
      the dsl builder
    • browseLimit

      Maximum number of messages to keep in memory available for browsing. Use 0 for unlimited. The option is a: int type. Default: 100 Group: advanced
      Parameters:
      browseLimit - the value to set
      Returns:
      the dsl builder
    • browseLimit

      Maximum number of messages to keep in memory available for browsing. Use 0 for unlimited. The option will be converted to a int type. Default: 100 Group: advanced
      Parameters:
      browseLimit - the value to set
      Returns:
      the dsl builder
    • destinationResolver

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder destinationResolver(org.springframework.jms.support.destination.DestinationResolver destinationResolver)
      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). The option is a: org.springframework.jms.support.destination.DestinationResolver type. Group: advanced
      Parameters:
      destinationResolver - the value to set
      Returns:
      the dsl builder
    • destinationResolver

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder destinationResolver(String destinationResolver)
      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). The option will be converted to a org.springframework.jms.support.destination.DestinationResolver type. Group: advanced
      Parameters:
      destinationResolver - the value to set
      Returns:
      the dsl builder
    • errorHandler

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder errorHandler(org.springframework.util.ErrorHandler errorHandler)
      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. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom errorHandler. The option is a: org.springframework.util.ErrorHandler type. Group: advanced
      Parameters:
      errorHandler - the value to set
      Returns:
      the dsl builder
    • errorHandler

      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. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom errorHandler. The option will be converted to a org.springframework.util.ErrorHandler type. Group: advanced
      Parameters:
      errorHandler - the value to set
      Returns:
      the dsl builder
    • exceptionListener

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder exceptionListener(jakarta.jms.ExceptionListener exceptionListener)
      Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. The option is a: jakarta.jms.ExceptionListener type. Group: advanced
      Parameters:
      exceptionListener - the value to set
      Returns:
      the dsl builder
    • exceptionListener

      Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. The option will be converted to a jakarta.jms.ExceptionListener type. Group: advanced
      Parameters:
      exceptionListener - the value to set
      Returns:
      the dsl builder
    • headerFilterStrategy

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder headerFilterStrategy(org.apache.camel.spi.HeaderFilterStrategy headerFilterStrategy)
      To use a custom HeaderFilterStrategy to filter header to and from Camel message. The option is a: org.apache.camel.spi.HeaderFilterStrategy type. Group: advanced
      Parameters:
      headerFilterStrategy - the value to set
      Returns:
      the dsl builder
    • headerFilterStrategy

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder headerFilterStrategy(String headerFilterStrategy)
      To use a custom HeaderFilterStrategy to filter header to and from Camel message. The option will be converted to a org.apache.camel.spi.HeaderFilterStrategy type. Group: advanced
      Parameters:
      headerFilterStrategy - the value to set
      Returns:
      the dsl builder
    • idleConsumerLimit

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder idleConsumerLimit(int idleConsumerLimit)
      Specify the limit for the number of consumers that are allowed to be idle at any given time. The option is a: int type. Default: 1 Group: advanced
      Parameters:
      idleConsumerLimit - the value to set
      Returns:
      the dsl builder
    • idleConsumerLimit

      Specify the limit for the number of consumers that are allowed to be idle at any given time. The option will be converted to a int type. Default: 1 Group: advanced
      Parameters:
      idleConsumerLimit - the value to set
      Returns:
      the dsl builder
    • idleReceivesPerTaskLimit

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder idleReceivesPerTaskLimit(int idleReceivesPerTaskLimit)
      Marks the consumer as idle after the specified number of idle receives have been reached. An idle receive is counted from the moment a null message is returned by the receiver after the potential setReceiveTimeout elapsed. This gives the opportunity to check if the idle task count exceeds setIdleTaskExecutionLimit and based on that decide if the task needs to be re-scheduled or not, saving resources that would otherwise be held. This setting differs from setMaxMessagesPerTask where the task is released and re-scheduled after this limit is reached, no matter if the received messages were null or non-null messages. This setting alone can be inflexible if one desires to have a large enough batch for each task but requires a quick(er) release from the moment there are no more messages to process. This setting differs from setIdleTaskExecutionLimit where this limit decides after how many iterations of being marked as idle, a task is released. For example: If setMaxMessagesPerTask is set to '500' and #setIdleReceivesPerTaskLimit is set to '60' and setReceiveTimeout is set to '1000' and setIdleTaskExecutionLimit is set to '1', then 500 messages per task would be processed unless there is a subsequent number of 60 idle messages received, the task would be marked as idle and released. This also means that after the last message was processed, the task would be released after 60 seconds as long as no new messages appear. The option is a: int type. Group: advanced
      Parameters:
      idleReceivesPerTaskLimit - the value to set
      Returns:
      the dsl builder
    • idleReceivesPerTaskLimit

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder idleReceivesPerTaskLimit(String idleReceivesPerTaskLimit)
      Marks the consumer as idle after the specified number of idle receives have been reached. An idle receive is counted from the moment a null message is returned by the receiver after the potential setReceiveTimeout elapsed. This gives the opportunity to check if the idle task count exceeds setIdleTaskExecutionLimit and based on that decide if the task needs to be re-scheduled or not, saving resources that would otherwise be held. This setting differs from setMaxMessagesPerTask where the task is released and re-scheduled after this limit is reached, no matter if the received messages were null or non-null messages. This setting alone can be inflexible if one desires to have a large enough batch for each task but requires a quick(er) release from the moment there are no more messages to process. This setting differs from setIdleTaskExecutionLimit where this limit decides after how many iterations of being marked as idle, a task is released. For example: If setMaxMessagesPerTask is set to '500' and #setIdleReceivesPerTaskLimit is set to '60' and setReceiveTimeout is set to '1000' and setIdleTaskExecutionLimit is set to '1', then 500 messages per task would be processed unless there is a subsequent number of 60 idle messages received, the task would be marked as idle and released. This also means that after the last message was processed, the task would be released after 60 seconds as long as no new messages appear. The option will be converted to a int type. Group: advanced
      Parameters:
      idleReceivesPerTaskLimit - the value to set
      Returns:
      the dsl builder
    • idleTaskExecutionLimit

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder idleTaskExecutionLimit(int idleTaskExecutionLimit)
      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. The option is a: int type. Default: 1 Group: advanced
      Parameters:
      idleTaskExecutionLimit - the value to set
      Returns:
      the dsl builder
    • idleTaskExecutionLimit

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder idleTaskExecutionLimit(String idleTaskExecutionLimit)
      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. The option will be converted to a int type. Default: 1 Group: advanced
      Parameters:
      idleTaskExecutionLimit - the value to set
      Returns:
      the dsl builder
    • includeAllJMSXProperties

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder includeAllJMSXProperties(boolean includeAllJMSXProperties)
      Whether to include all JMSX prefixed 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. The option is a: boolean type. Default: false Group: advanced
      Parameters:
      includeAllJMSXProperties - the value to set
      Returns:
      the dsl builder
    • includeAllJMSXProperties

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder includeAllJMSXProperties(String includeAllJMSXProperties)
      Whether to include all JMSX prefixed 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. The option will be converted to a boolean type. Default: false Group: advanced
      Parameters:
      includeAllJMSXProperties - the value to set
      Returns:
      the dsl builder
    • jmsKeyFormatStrategy

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder jmsKeyFormatStrategy(org.apache.camel.component.jms.JmsKeyFormatStrategy jmsKeyFormatStrategy)
      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. The option is a: org.apache.camel.component.jms.JmsKeyFormatStrategy type. Group: advanced
      Parameters:
      jmsKeyFormatStrategy - the value to set
      Returns:
      the dsl builder
    • jmsKeyFormatStrategy

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder jmsKeyFormatStrategy(String jmsKeyFormatStrategy)
      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. The option will be converted to a org.apache.camel.component.jms.JmsKeyFormatStrategy type. Group: advanced
      Parameters:
      jmsKeyFormatStrategy - the value to set
      Returns:
      the dsl builder
    • mapJmsMessage

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder mapJmsMessage(boolean mapJmsMessage)
      Specifies whether Camel should auto map the received JMS message to a suited payload type, such as jakarta.jms.TextMessage to a String etc. The option is a: boolean type. Default: true Group: advanced
      Parameters:
      mapJmsMessage - the value to set
      Returns:
      the dsl builder
    • mapJmsMessage

      Specifies whether Camel should auto map the received JMS message to a suited payload type, such as jakarta.jms.TextMessage to a String etc. The option will be converted to a boolean type. Default: true Group: advanced
      Parameters:
      mapJmsMessage - the value to set
      Returns:
      the dsl builder
    • maxMessagesPerTask

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder maxMessagesPerTask(int maxMessagesPerTask)
      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. The option is a: int type. Default: -1 Group: advanced
      Parameters:
      maxMessagesPerTask - the value to set
      Returns:
      the dsl builder
    • maxMessagesPerTask

      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. The option will be converted to a int type. Default: -1 Group: advanced
      Parameters:
      maxMessagesPerTask - the value to set
      Returns:
      the dsl builder
    • messageConverter

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder messageConverter(org.springframework.jms.support.converter.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 jakarta.jms.Message. The option is a: org.springframework.jms.support.converter.MessageConverter type. Group: advanced
      Parameters:
      messageConverter - the value to set
      Returns:
      the dsl builder
    • messageConverter

      To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a jakarta.jms.Message. The option will be converted to a org.springframework.jms.support.converter.MessageConverter type. Group: advanced
      Parameters:
      messageConverter - the value to set
      Returns:
      the dsl builder
    • messageCreatedStrategy

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder messageCreatedStrategy(org.apache.camel.component.jms.MessageCreatedStrategy messageCreatedStrategy)
      To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of jakarta.jms.Message objects when Camel is sending a JMS message. The option is a: org.apache.camel.component.jms.MessageCreatedStrategy type. Group: advanced
      Parameters:
      messageCreatedStrategy - the value to set
      Returns:
      the dsl builder
    • messageCreatedStrategy

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder messageCreatedStrategy(String messageCreatedStrategy)
      To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of jakarta.jms.Message objects when Camel is sending a JMS message. The option will be converted to a org.apache.camel.component.jms.MessageCreatedStrategy type. Group: advanced
      Parameters:
      messageCreatedStrategy - the value to set
      Returns:
      the dsl builder
    • messageIdEnabled

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder messageIdEnabled(boolean messageIdEnabled)
      When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value. The option is a: boolean type. Default: true Group: advanced
      Parameters:
      messageIdEnabled - the value to set
      Returns:
      the dsl builder
    • messageIdEnabled

      When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value. The option will be converted to a boolean type. Default: true Group: advanced
      Parameters:
      messageIdEnabled - the value to set
      Returns:
      the dsl builder
    • messageListenerContainerFactory

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder messageListenerContainerFactory(org.apache.camel.component.jms.MessageListenerContainerFactory messageListenerContainerFactory)
      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. The option is a: org.apache.camel.component.jms.MessageListenerContainerFactory type. Group: advanced
      Parameters:
      messageListenerContainerFactory - the value to set
      Returns:
      the dsl builder
    • messageListenerContainerFactory

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder messageListenerContainerFactory(String messageListenerContainerFactory)
      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. The option will be converted to a org.apache.camel.component.jms.MessageListenerContainerFactory type. Group: advanced
      Parameters:
      messageListenerContainerFactory - the value to set
      Returns:
      the dsl builder
    • messageTimestampEnabled

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder messageTimestampEnabled(boolean messageTimestampEnabled)
      Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value. The option is a: boolean type. Default: true Group: advanced
      Parameters:
      messageTimestampEnabled - the value to set
      Returns:
      the dsl builder
    • messageTimestampEnabled

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder messageTimestampEnabled(String messageTimestampEnabled)
      Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value. The option will be converted to a boolean type. Default: true Group: advanced
      Parameters:
      messageTimestampEnabled - the value to set
      Returns:
      the dsl builder
    • pubSubNoLocal

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder pubSubNoLocal(boolean pubSubNoLocal)
      Specifies whether to inhibit the delivery of messages published by its own connection. The option is a: boolean type. Default: false Group: advanced
      Parameters:
      pubSubNoLocal - the value to set
      Returns:
      the dsl builder
    • pubSubNoLocal

      Specifies whether to inhibit the delivery of messages published by its own connection. The option will be converted to a boolean type. Default: false Group: advanced
      Parameters:
      pubSubNoLocal - the value to set
      Returns:
      the dsl builder
    • receiveTimeout

      The timeout for receiving messages (in milliseconds). The option is a: long type. Default: 1000 Group: advanced
      Parameters:
      receiveTimeout - the value to set
      Returns:
      the dsl builder
    • receiveTimeout

      The timeout for receiving messages (in milliseconds). The option will be converted to a long type. Default: 1000 Group: advanced
      Parameters:
      receiveTimeout - the value to set
      Returns:
      the dsl builder
    • recoveryInterval

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder recoveryInterval(long recoveryInterval)
      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. The option is a: long type. Default: 5000 Group: advanced
      Parameters:
      recoveryInterval - the value to set
      Returns:
      the dsl builder
    • recoveryInterval

      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. The option will be converted to a long type. Default: 5000 Group: advanced
      Parameters:
      recoveryInterval - the value to set
      Returns:
      the dsl builder
    • requestTimeoutCheckerInterval

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder requestTimeoutCheckerInterval(long requestTimeoutCheckerInterval)
      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. The option is a: long type. Default: 1000 Group: advanced
      Parameters:
      requestTimeoutCheckerInterval - the value to set
      Returns:
      the dsl builder
    • requestTimeoutCheckerInterval

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder requestTimeoutCheckerInterval(String requestTimeoutCheckerInterval)
      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. The option will be converted to a long type. Default: 1000 Group: advanced
      Parameters:
      requestTimeoutCheckerInterval - the value to set
      Returns:
      the dsl builder
    • synchronous

      Sets whether synchronous processing should be strictly used. The option is a: boolean type. Default: false Group: advanced
      Parameters:
      synchronous - the value to set
      Returns:
      the dsl builder
    • synchronous

      Sets whether synchronous processing should be strictly used. The option will be converted to a boolean type. Default: false Group: advanced
      Parameters:
      synchronous - the value to set
      Returns:
      the dsl builder
    • temporaryQueueResolver

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder temporaryQueueResolver(org.apache.camel.component.jms.TemporaryQueueResolver temporaryQueueResolver)
      A pluggable TemporaryQueueResolver that allows you to use your own resolver for creating temporary queues (some messaging systems has special requirements for creating temporary queues). The option is a: org.apache.camel.component.jms.TemporaryQueueResolver type. Group: advanced
      Parameters:
      temporaryQueueResolver - the value to set
      Returns:
      the dsl builder
    • temporaryQueueResolver

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder temporaryQueueResolver(String temporaryQueueResolver)
      A pluggable TemporaryQueueResolver that allows you to use your own resolver for creating temporary queues (some messaging systems has special requirements for creating temporary queues). The option will be converted to a org.apache.camel.component.jms.TemporaryQueueResolver type. Group: advanced
      Parameters:
      temporaryQueueResolver - the value to set
      Returns:
      the dsl builder
    • transferException

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder transferException(boolean transferException)
      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 jakarta.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. Use this with caution as the data is using Java Object serialization and requires the received to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumer!. The option is a: boolean type. Default: false Group: advanced
      Parameters:
      transferException - the value to set
      Returns:
      the dsl builder
    • transferException

      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 jakarta.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. Use this with caution as the data is using Java Object serialization and requires the received to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumer!. The option will be converted to a boolean type. Default: false Group: advanced
      Parameters:
      transferException - the value to set
      Returns:
      the dsl builder
    • transferExchange

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder transferExchange(boolean transferExchange)
      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. Use this with caution as the data is using Java Object serialization and requires the receiver to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumers having to use compatible Camel versions!. The option is a: boolean type. Default: false Group: advanced
      Parameters:
      transferExchange - the value to set
      Returns:
      the dsl builder
    • transferExchange

      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. Use this with caution as the data is using Java Object serialization and requires the receiver to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumers having to use compatible Camel versions!. The option will be converted to a boolean type. Default: false Group: advanced
      Parameters:
      transferExchange - the value to set
      Returns:
      the dsl builder
    • useMessageIDAsCorrelationID

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder useMessageIDAsCorrelationID(boolean useMessageIDAsCorrelationID)
      Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. The option is a: boolean type. Default: false Group: advanced
      Parameters:
      useMessageIDAsCorrelationID - the value to set
      Returns:
      the dsl builder
    • useMessageIDAsCorrelationID

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder useMessageIDAsCorrelationID(String useMessageIDAsCorrelationID)
      Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. The option will be converted to a boolean type. Default: false Group: advanced
      Parameters:
      useMessageIDAsCorrelationID - the value to set
      Returns:
      the dsl builder
    • waitForProvisionCorrelationToBeUpdatedCounter

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder waitForProvisionCorrelationToBeUpdatedCounter(int waitForProvisionCorrelationToBeUpdatedCounter)
      Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled. The option is a: int type. Default: 50 Group: advanced
      Parameters:
      waitForProvisionCorrelationToBeUpdatedCounter - the value to set
      Returns:
      the dsl builder
    • waitForProvisionCorrelationToBeUpdatedCounter

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder waitForProvisionCorrelationToBeUpdatedCounter(String waitForProvisionCorrelationToBeUpdatedCounter)
      Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled. The option will be converted to a int type. Default: 50 Group: advanced
      Parameters:
      waitForProvisionCorrelationToBeUpdatedCounter - the value to set
      Returns:
      the dsl builder
    • waitForProvisionCorrelationToBeUpdatedThreadSleepingTime

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder waitForProvisionCorrelationToBeUpdatedThreadSleepingTime(long waitForProvisionCorrelationToBeUpdatedThreadSleepingTime)
      Interval in millis to sleep each time while waiting for provisional correlation id to be updated. The option is a: long type. Default: 100 Group: advanced
      Parameters:
      waitForProvisionCorrelationToBeUpdatedThreadSleepingTime - the value to set
      Returns:
      the dsl builder
    • waitForProvisionCorrelationToBeUpdatedThreadSleepingTime

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder waitForProvisionCorrelationToBeUpdatedThreadSleepingTime(String waitForProvisionCorrelationToBeUpdatedThreadSleepingTime)
      Interval in millis to sleep each time while waiting for provisional correlation id to be updated. The option will be converted to a long type. Default: 100 Group: advanced
      Parameters:
      waitForProvisionCorrelationToBeUpdatedThreadSleepingTime - the value to set
      Returns:
      the dsl builder
    • waitForTemporaryReplyToToBeUpdatedCounter

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder waitForTemporaryReplyToToBeUpdatedCounter(int waitForTemporaryReplyToToBeUpdatedCounter)
      Number of times to wait for temporary replyTo queue to be created and ready when doing request/reply over JMS. The option is a: int type. Default: 200 Group: advanced
      Parameters:
      waitForTemporaryReplyToToBeUpdatedCounter - the value to set
      Returns:
      the dsl builder
    • waitForTemporaryReplyToToBeUpdatedCounter

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder waitForTemporaryReplyToToBeUpdatedCounter(String waitForTemporaryReplyToToBeUpdatedCounter)
      Number of times to wait for temporary replyTo queue to be created and ready when doing request/reply over JMS. The option will be converted to a int type. Default: 200 Group: advanced
      Parameters:
      waitForTemporaryReplyToToBeUpdatedCounter - the value to set
      Returns:
      the dsl builder
    • waitForTemporaryReplyToToBeUpdatedThreadSleepingTime

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder waitForTemporaryReplyToToBeUpdatedThreadSleepingTime(long waitForTemporaryReplyToToBeUpdatedThreadSleepingTime)
      Interval in millis to sleep each time while waiting for temporary replyTo queue to be ready. The option is a: long type. Default: 100 Group: advanced
      Parameters:
      waitForTemporaryReplyToToBeUpdatedThreadSleepingTime - the value to set
      Returns:
      the dsl builder
    • waitForTemporaryReplyToToBeUpdatedThreadSleepingTime

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder waitForTemporaryReplyToToBeUpdatedThreadSleepingTime(String waitForTemporaryReplyToToBeUpdatedThreadSleepingTime)
      Interval in millis to sleep each time while waiting for temporary replyTo queue to be ready. The option will be converted to a long type. Default: 100 Group: advanced
      Parameters:
      waitForTemporaryReplyToToBeUpdatedThreadSleepingTime - the value to set
      Returns:
      the dsl builder
    • lazyCreateTransactionManager

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder lazyCreateTransactionManager(boolean lazyCreateTransactionManager)
      If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. The option is a: boolean type. Default: true Group: transaction (advanced)
      Parameters:
      lazyCreateTransactionManager - the value to set
      Returns:
      the dsl builder
    • lazyCreateTransactionManager

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder lazyCreateTransactionManager(String lazyCreateTransactionManager)
      If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. The option will be converted to a boolean type. Default: true Group: transaction (advanced)
      Parameters:
      lazyCreateTransactionManager - the value to set
      Returns:
      the dsl builder
    • transactionManager

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder transactionManager(org.springframework.transaction.PlatformTransactionManager transactionManager)
      The Spring transaction manager to use. The option is a: org.springframework.transaction.PlatformTransactionManager type. Group: transaction (advanced)
      Parameters:
      transactionManager - the value to set
      Returns:
      the dsl builder
    • transactionManager

      The Spring transaction manager to use. The option will be converted to a org.springframework.transaction.PlatformTransactionManager type. Group: transaction (advanced)
      Parameters:
      transactionManager - the value to set
      Returns:
      the dsl builder
    • transactionName

      The name of the transaction to use. The option is a: java.lang.String type. Group: transaction (advanced)
      Parameters:
      transactionName - the value to set
      Returns:
      the dsl builder
    • transactionTimeout

      default ActiveMQ6EndpointBuilderFactory.AdvancedActiveMQ6EndpointProducerBuilder transactionTimeout(int transactionTimeout)
      The timeout value of the transaction (in seconds), if using transacted mode. The option is a: int type. Default: -1 Group: transaction (advanced)
      Parameters:
      transactionTimeout - the value to set
      Returns:
      the dsl builder
    • transactionTimeout

      The timeout value of the transaction (in seconds), if using transacted mode. The option will be converted to a int type. Default: -1 Group: transaction (advanced)
      Parameters:
      transactionTimeout - the value to set
      Returns:
      the dsl builder