Skip to main content

JMS parameters

Query Parameter

From Version

DefaultValue

Description

conduitIdSelectorPrefix

3.0.0

If set then this string will be the prefix for all correlation ids the conduit creates and also be used in the selector for listening to replies

deliveryMode

PERSISTENT

NON_PERSISTENT messages will kept only in memory

PERSISTENT messages will be saved to disk

durableSubscriptionClientId

3.0.1

Optional Client identifier for the connection. The purpose is to associate a connection with a state maintained on behalf of the client by a provider. The only such state identified by the JMS API is that required to support durable subscriptions.

durableSubscriptionName

3.0.0

jndiConnectionFactoryName

ConnectionFactory

Specifies the JNDI name bound to the JMS connection factory to use when connecting to the JMS destination.

jndiInitialContextFactory

Specifies the fully qualified Java class name of the "InitialContextFactory" implementation class to use.

jndiTransactionManagerName

3.0.0

Name of the JTA TransactionManager. Will be searched in spring, blueprint and jndi.

If a transaction manager is found then JTA transactions will be enabled. See details below.

jndiURL

Specifies the JNDI provider URL

jndi-*

Additional parameters for a JNDI provider

messageType

3.0.0

byte

JMS message type used by CXF (byte, text or binary)

password

3.0.0

Password for creating the connection. Using this in the URI is discouraged

priority

3.0.0

4

Priority for the messages. See your JMS provider documentation for details. Values range from 0 to 9 where 0 is lowest priority

replyToName

Specifies the JNDI name bound to the JMS destinations where replies are sent

receiveTimeout

3.0.0

60000

Timeout in milliseconds the client waits for a reply in case of request / repy exchanges

reconnectOnException

deprecated in 3.0.0

true

Should the transport reconnect in case of exceptions. From version 3.0.0 on the transport will always reconnect in case of exceptions

sessionTransacted

3.0.0

false

Set to true for resource local transactions. Do not set if you use JTA

timeToLive

0

Time (in ms) after which the message will be discarded by the jms provider

topicReplyToName

Reply to messages on a topic with this name. Depending on the variant this is either a jndi or jms name.

useConduitIdSelector

3.0.0

true

Each conduit is assigned with a UUID. If set to true this conduit id will be the prefix for all correlation ids. This allows several endpoints to share a JMS queue or topic

username

3.0.0

Username for creating the connection

Some of these attributes are specified in the JMS URI specification.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!