# JMSConfiguration options

| Name | Description |
| --- | --- |
| connectionFactory | Mandatory field. Reference to a bean that defines a jms ConnectionFactory.<br>Remember to wrap the connectionFactory like described above when not using a<br>pooling ConnectionFactory |
| wrapInSingleConnectionFactory | This option was removed since CXF 3.0.0. Will wrap the connectionFactory<br>with a Spring SingleConnectionFactory, which can improve the performance of the<br>jms transport. Default is true. |
| reconnectOnException | (deprecated) If wrapping the connectionFactory with a Spring<br>SingleConnectionFactory and reconnectOnException is true, will create a new<br>connection if there is an exception thrown, otherwise will not try to reconnect<br>if the there is an exception thrown. Default is false. From CXF 3.0.0, CXF<br>always reconnect on exceptions |
| targetDestination | JNDI name or provider specific name of a destination. Example for ActiveMQ:<br>test.cxf.jmstransport.queue |
| destinationResolver | Reference to a Spring DestinationResolver. This allows to define how<br>destination names are resolved to jms Destinations. By default a<br>DynamicDestinationResolver is used. It resolves destinations using the jms<br>providers features. If you reference a JndiDestinationResolver you can resolve<br>the destination names using JNDI. |
| transactionManager | Reference to a Spring transaction manager. This allows to take part in JTA<br>Transactions with your webservice. You can also register a spring JMS<br>Transaction Manager to have local transactions. |
| taskExecutor | This option was removed since CXF 3.0.0. Reference to a Spring TaskExecutor.<br>This is used in listeners to decide how to handle incoming messages. Default is<br>a Spring SimpleAsyncTaskExecutor. |
| useJms11 | This option was removed since CXF 3.0.0. true means JMS 1.1 features are<br>used false means only JMS 1.0.2 features are used. Default is<br>false. |
| messageIdEnabled | Default is true. This option was removed since CXF 3.0.0. |
| messageTimestampEnabled | Default is true. This option was removed since CXF 3.0.0. |
| cacheLevel | This option was removed since CXF 3.0.0. Specify the level of caching that<br>the JMS listener container is allowed to apply. (Default is -1)<br>Please check out the java doc of the org.springframework. jms.listener.<br>DefaultMessageListenerContainer for more information |
| pubSubNoLocal | If true do not receive your own messages when using topics. Default is<br>false. |
| receiveTimeout | How many milliseconds to wait for response messages. 0 (default) means wait<br>indefinitely. since CXF 3.0, the default value is changed to 60000<br>(60 seconds) |
| explicitQosEnabled | If true, means that QoS parameters are set for each message. (Default is<br>false.) |
| deliveryMode | NON\_PERSISTENT = 1 messages will only be kept in<br>memory<br><br>PERSISTENT = 2 (default) messages will be persisted to disk |
| priority | Priority for the messages. Default is 4. See your JMS provider doc for<br>details. |
| timeToLive | After this time the message will be discarded by the jms provider. Default<br>is 0. |
| sessionTransacted | If true, means JMS transactions are used. Default is false. In 2.7.x you<br>will also need to register a JMS Transaction Manager with JMSConfiguration in<br>order for transactions to be enabled. |
| concurrentConsumers | This option was removed since CXF 3.0.0. Minimum number of concurrent<br>consumers for listener (default is 1). |
| maxConcurrentConsumers | This option was removed since CXF 3.0.0. Maximum number of concurrent<br>consumers for listener (default 1). |
| maxConcurrentTasks | This option was removed since CXF 3.0.0. (deprecated) Maximum number of<br>threads that handle the received requests. Default 10. |
| messageSelector | jms selector to filter incoming messages (allows to share a queue) |
| subscriptionDurable | Default is false. |
| durableSubscriptionName |  |
| messageType | text (default) binary byte |
| pubSubDomain | false (default) means use queues true means use topics |
| jmsProviderTibcoEms | True means that the jms provider is Tibco EMS. Default is false. Currently<br>this activates that the principal in the SecurityContext is populated from the<br>header JMS\_TIBCO\_SENDER. (available from cxf version 2.2.6) |
| maxSuspendedContinuations | Since CXF 3.0.0, The max suspended<br>continuations that the JMS destination could have, if the current suspended<br>continuations number exceeds the max value, the JMSListenerContainer will be<br>stopped. The default value is -1, which means disable this feature. |
| reconnectPercentOfMax | Since CXF 3.0.0, If the<br>JMSListenerContainer is stopped due to the current suspended continuation<br>exceeds the max value, the JMSListenerContainer will be restarted when the<br>current suspended continuation below the value of<br>(maxSuspendedContinuations\*reconnectPercentOfMax/100). The default value is<br>70. |
| createSecurityContext | (Since 2.7.14, 3.0.3) true (default) means<br>create user security context for incoming messages. |
| propogateExceptions | (Since 2.7.15) 2.7.x only true (default)<br>means that any exceptions occurring while processing the incoming message will<br>be propagated. This setting is only relevant when a transaction manager and<br>sessionTransacted are set. |