Interface ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder

  • All Superinterfaces:
    org.apache.camel.builder.EndpointConsumerBuilder, org.apache.camel.EndpointConsumerResolver
    All Known Subinterfaces:
    ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointBuilder
    Enclosing interface:
    ActiveMQEndpointBuilderFactory

    public static interface ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder
    extends org.apache.camel.builder.EndpointConsumerBuilder
    Advanced builder for endpoint consumers for the ActiveMQ component.
    • Method Detail

      • acceptMessagesWhileStopping

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder acceptMessagesWhileStopping​(boolean acceptMessagesWhileStopping)
        Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead letter queue on the JMS broker. To avoid this its recommended to enable this option. The option is a: boolean type. Default: false Group: consumer (advanced)
      • acceptMessagesWhileStopping

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder acceptMessagesWhileStopping​(String acceptMessagesWhileStopping)
        Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead letter queue on the JMS broker. To avoid this its recommended to enable this option. The option will be converted to a boolean type. Default: false Group: consumer (advanced)
      • allowReplyManagerQuickStop

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder allowReplyManagerQuickStop​(boolean allowReplyManagerQuickStop)
        Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this flag. The option is a: boolean type. Default: false Group: consumer (advanced)
      • allowReplyManagerQuickStop

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder allowReplyManagerQuickStop​(String allowReplyManagerQuickStop)
        Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this flag. The option will be converted to a boolean type. Default: false Group: consumer (advanced)
      • consumerType

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder consumerType​(ActiveMQEndpointBuilderFactory.ConsumerType consumerType)
        The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use. The option is a: org.apache.camel.component.jms.ConsumerType type. Default: Default Group: consumer (advanced)
      • consumerType

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder consumerType​(String consumerType)
        The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use. The option will be converted to a org.apache.camel.component.jms.ConsumerType type. Default: Default Group: consumer (advanced)
      • defaultTaskExecutorType

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder defaultTaskExecutorType​(ActiveMQEndpointBuilderFactory.DefaultTaskExecutorType defaultTaskExecutorType)
        Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints and SimpleAsync for reply consumers. The use of ThreadPool is recommended to reduce thread trash in elastic configurations with dynamically increasing and decreasing concurrent consumers. The option is a: org.apache.camel.component.jms.DefaultTaskExecutorType type. Group: consumer (advanced)
      • defaultTaskExecutorType

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder defaultTaskExecutorType​(String defaultTaskExecutorType)
        Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints and SimpleAsync for reply consumers. The use of ThreadPool is recommended to reduce thread trash in elastic configurations with dynamically increasing and decreasing concurrent consumers. The option will be converted to a org.apache.camel.component.jms.DefaultTaskExecutorType type. Group: consumer (advanced)
      • eagerLoadingOfProperties

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder eagerLoadingOfProperties​(boolean eagerLoadingOfProperties)
        Enables eager loading of JMS properties and payload as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerPoisonBody. The option is a: boolean type. Default: false Group: consumer (advanced)
      • eagerLoadingOfProperties

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder eagerLoadingOfProperties​(String eagerLoadingOfProperties)
        Enables eager loading of JMS properties and payload as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerPoisonBody. The option will be converted to a boolean type. Default: false Group: consumer (advanced)
      • eagerPoisonBody

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder eagerPoisonBody​(String eagerPoisonBody)
        If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody=false. See also the option eagerLoadingOfProperties. The option is a: java.lang.String type. Default: Poison JMS message due to ${exception.message} Group: consumer (advanced)
      • exceptionHandler

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder exceptionHandler​(org.apache.camel.spi.ExceptionHandler exceptionHandler)
        To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. The option is a: org.apache.camel.spi.ExceptionHandler type. Group: consumer (advanced)
      • exceptionHandler

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder exceptionHandler​(String exceptionHandler)
        To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. The option will be converted to a org.apache.camel.spi.ExceptionHandler type. Group: consumer (advanced)
      • replyToSameDestinationAllowed

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder replyToSameDestinationAllowed​(boolean replyToSameDestinationAllowed)
        Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself. The option is a: boolean type. Default: false Group: consumer (advanced)
      • replyToSameDestinationAllowed

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder replyToSameDestinationAllowed​(String replyToSameDestinationAllowed)
        Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself. The option will be converted to a boolean type. Default: false Group: consumer (advanced)
      • allowSerializedHeaders

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • allowSerializedHeaders

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • asyncStartListener

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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 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. The option is a: boolean type. Default: false Group: advanced
      • asyncStartListener

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder asyncStartListener​(String 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 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. The option will be converted to a boolean type. Default: false Group: advanced
      • destinationResolver

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder destinationResolver​(Object 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
      • destinationResolver

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • errorHandler

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder errorHandler​(Object 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
      • errorHandler

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder errorHandler​(String 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
      • headerFilterStrategy

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • idleTaskExecutionLimit

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • idleTaskExecutionLimit

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • includeAllJMSXProperties

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder includeAllJMSXProperties​(boolean includeAllJMSXProperties)
        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. The option is a: boolean type. Default: false Group: advanced
      • includeAllJMSXProperties

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder includeAllJMSXProperties​(String includeAllJMSXProperties)
        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. The option will be converted to a boolean type. Default: false Group: advanced
      • jmsKeyFormatStrategy

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder jmsKeyFormatStrategy​(Object 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
      • jmsKeyFormatStrategy

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • maxMessagesPerTask

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • maxMessagesPerTask

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder maxMessagesPerTask​(String 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
      • messageConverter

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder messageConverter​(Object 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. The option is a: org.springframework.jms.support.converter.MessageConverter type. Group: advanced
      • messageConverter

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder messageConverter​(String 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. The option will be converted to a org.springframework.jms.support.converter.MessageConverter type. Group: advanced
      • messageCreatedStrategy

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder messageCreatedStrategy​(Object messageCreatedStrategy)
        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. The option is a: org.apache.camel.component.jms.MessageCreatedStrategy type. Group: advanced
      • messageCreatedStrategy

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder messageCreatedStrategy​(String messageCreatedStrategy)
        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. The option will be converted to a org.apache.camel.component.jms.MessageCreatedStrategy type. Group: advanced
      • messageIdEnabled

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • messageIdEnabled

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder messageIdEnabled​(String 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
      • messageListenerContainerFactory

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder messageListenerContainerFactory​(Object 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
      • messageListenerContainerFactory

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • messageTimestampEnabled

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • messageTimestampEnabled

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • recoveryInterval

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • requestTimeoutCheckerInterval

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • requestTimeoutCheckerInterval

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • transferException

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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 javax.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
      • transferException

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder transferException​(String 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 javax.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
      • transferExchange

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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 received to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumer having to use compatible Camel versions!. The option is a: boolean type. Default: false Group: advanced
      • transferExchange

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder transferExchange​(String 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 received to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumer having to use compatible Camel versions!. The option will be converted to a boolean type. Default: false Group: advanced
      • waitForProvisionCorrelationToBeUpdatedCounter

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • waitForProvisionCorrelationToBeUpdatedCounter

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • waitForProvisionCorrelationToBeUpdatedThreadSleepingTime

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • waitForProvisionCorrelationToBeUpdatedThreadSleepingTime

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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
      • lazyCreateTransactionManager

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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)
      • lazyCreateTransactionManager

        default ActiveMQEndpointBuilderFactory.AdvancedActiveMQEndpointConsumerBuilder 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)