Child pages
  • JMS

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: CAMEL-246 allowed the username and password to be specified on the JMSComponent

...

Property

Default Value

Description

acceptMessagesWhileStopping

false

Should the consumer accept messages while it is stopping

acknowledgementModeName

"AUTO_ACKNOWLEDGE"

The JMS acknowledgement name which is one of: TRANSACTED, CLIENT_ACKNOWLEDGE, AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE

acknowledgementMode

-1

The JMS acknowledgement mode defined as an Integer. Allows to set vendor-specific extensions to the acknowledgment mode. For the regular modes prefer to use the acknowledgementModeName instead.

alwaysCopyMessage

false

If true then Camel will always make a JMS message copy of the message when it's passed to the producer for sending. Copying the message is needed in some situations such as when a replyToDestinationSelectorName is set (Camel will by the way set the alwaysCopyMessage to true if a replyToDestinationSelectorName is set)

autoStartup

true

Should the consumer container auto-startup

cacheLevelName

"CACHE_CONSUMER"

Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO, CACHE_CONNECTION, CACHE_CONSUMER, CACHE_NONE and CACHE_SESSION. See the Spring documentation.

cacheLevel

-1

Sets the cache level by id for the underlying JMS resources

clientId

null

Sets the JMS client ID to use. Note that this value if specified must be unique and can only be used by a single JMS connection instance. Its typically only required for durable topic subscriptions. You may prefer to use Virtual Topics instead

consumerType

Default

The consumer type to use, either: Simple, Default or ServerSessionPool. The consumer type determines which Spring JMS listener should be used. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer. Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer and ServerSessionPool will use org.springframework.jms.listener.serversession.ServerSessionMessageListenerContainer. If option useVersion102=true then Camel will of course use the JMS 1.0.2 Spring classes instead. ServerSessionPool is @deprecated and will be removed in Camel 2.0.

concurrentConsumers

1

Specifies the default number of concurrent consumers

connectionFactory

null

The default JMS connection factory to use for the listenerConnectionFactory and templateConnectionFactory if neither are specified

deliveryPersistent

true

Is persistent delivery used by default?

disableReplyTo

false

Do you want to ignore the JMSReplyTo header and so treat messages as InOnly by default and not send a reply back?

durableSubscriptionName

null

The durable subscriber name for specifying durable topic subscriptions

eagerLoadingOfProperties

false

Enables eager loading of JMS properties as soon as a message is received 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. Can be used for testing purpose to ensure JMS properties can be understood and handled correctly.

exceptionListener

null

The JMS Exception Listener used to be notified of any underlying JMS exceptions

explicitQosEnabled

false

Set if the deliveryMode, priority or timeToLive should be used when sending messages

exposeListenerSession

true

Set if the listener session should be exposed when consuming messages

idleTaskExecutionLimit

1

Specify 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 case of dynamic scheduling; see the "maxConcurrentConsumers" setting).

jmsOperations

null

Allow to use your own implementation of the org.springframework.jms.core.JmsOperations interface. Camel uses JmsTemplate as default. Can be used for testing purpose, but not used much as stated in the spring API docs.

listenerConnectionFactory

null

The JMS connection factory used for consuming messages

maxConcurrentConsumers

1

Specifies the maximum number of concurrent consumers

maxMessagesPerTask

1

The number of messages per task

messageConverter

null

The Spring Message Converter

messageIdEnabled

true

When sending, should message IDs be added

messageTimestampEnabled

true

Should timestamps be enabled by default on sending messages

password

null

The password which is set for the connector factory

priority

-1

Values of > 1 specify the message priority when sending, if the explicitQosEnabled property is specified (with 0 as the lowest priority and 9 as the highest)

preserveMessageQos

false

Set to true if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint

pubSubNoLocal

false

Set whether to inhibit the delivery of messages published by its own connection

selector

null

Sets the JMS Selector which is an SQL 92 predicate used to apply to messages to filter them at the message broker. You may have to encode special characters such as = as %3D

receiveTimeout

none

The timeout when receiving messages

recoveryInterval

none

The recovery interval

replyToTempDestinationAffinity

endpoint

defines the component created temporary replyTo destination sharing strategy. Possible values are: component, endpoint or producer. component = a single temp queue is shared among all producers for a given component instance. endpoint = a single temp queue is shared among all producers for a given endpoint instance. producer = a single temp queue is created per producer.

replyToDestination

null

Provides an explicit reply to destination which overrides any incoming value of Message.getJMSReplyTo()

replyToDestinationSelectorName

null

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 (i.e. if you are not using a temporary reply queue).

replyToDeliveryPersistent

true

Is persistent delivery used by default for reply?

requestTimeout

20000

The timeout when sending messages

serverSessionFactory

null

@deprecated - will be removed in Camel 2.0. The JMS ServerSessionFactory if you wish to use ServerSessionFactory for consumption

subscriptionDurable

false

Enabled by default if you specify a durableSubscriberName and a clientId

taskExecutor

null

Allows you to specify a custom task executor for consuming messages

templateConnectionFactory

null

The JMS connection factory used for sending messages

timeToLive

null

Is a time to live specified when sending messages

transacted

false

Is transacted mode used for sending/receiving messages?

transactionManager

null

The Spring transaction manager to use

transactionName

null

The name of the transaction to use

transactionTimeout

null

The timeout value of the transaction if using transacted mode

username

null

The username which is set for the connector factory

useMessageIDAsCorrelationID

false

Should JMSMessageID be used as JMSCorrelationID for InOut messages. Camel will by default use a GUID

useVersion102

false

Should the old JMS API be used

...