This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • SJMS

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Div
classconfluenceTableSmall

Option

Required

Default Value

Description

connectionCount

 

1

The maximum number of connections available to endpoints started under this component

connectionFactory

(tick)

null

A ConnectionFactory is required to enable the SjmsComponent. It can be set directly or set set as part of a ConnectionResource.

connectionResource

 

null

A ConnectionResource is an interface that allows for customization and container control of the ConnectionFactory. See Plugable Connection Resource Management for further details.

headerFilterStrategy

 

DefaultJmsKeyFormatStrategy

 

keyFormatStrategy

 

DefaultJmsKeyFormatStrategy

Camel 2.15.x or older: See option below

jmsKeyFormatStrategy DefaultJmsKeyFormatStrategy*Camel 2.16:* 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 theorg.apache.camel.component.jms.JmsKeyFormatStrategy and refer to it using the # notation.

transactionCommitStrategy

 

null

 

DestinationCreationStrategy DefaultDestinationCreationStrategySince Camel 2.15.0: Support to set the custom DestinationCreationStrategy on the SJMS Component.
messageCreatedStrategy  Camel 2.16: 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.

Below is an example of how to configure the SjmsComponent with its required ConnectionFactory provider. It will create a single connection by default and store it using the components internal pooling APIs to ensure that it is able to service Session creation requests in a thread safe manner.

...