...
If you're using ActiveMQ, the ActiveMQ connection pool from the Jencks AMQPool. Just add jencks-amqpool to your classpath. Then you can define a connection pool the following way:
Code Block | ||
---|---|---|
| ||
<beans xmlns:amqpool="http://jencks.org/amqpool/2.0"> <amqpool:xa-pool id="connectionFactory" url="tcp://localhost:61616" transactionManager="#transactionManager" /> </beans> |
See the Jencks AMQPool documentation from the Jencks project for more information.
...
Warning | ||
---|---|---|
| ||
The listener cacheLevel defaults to CACHE_NONE, which means no jms resources are cached at all. If your consumer consumes any volume of messages your you should set this to at least CACHE_CONNECTION (cacheLevel="1") or for optimal consumer performance use CACHE_CONSUMER (cacheLevel="3") |
...
Code Block | ||
---|---|---|
| ||
<jms:soap-provider wsdl="classpath:service.wsdl" destinationName="my.queue" connectionFactory="#connectionFactory" /> |
<jms:provider/>
Name | Type | Default | Description | Required |
---|---|---|---|---|
preserveQos | boolean | | When set to | false |
<jms:provider/>
Name | Type | Default | Description | Required |
---|---|---|---|---|
preserveQos | boolean | | When set to | false |
The Connection Factory
ActiveMQ
...
Code Block | ||
---|---|---|
| ||
<beans xmlns:amqpool="http://jencks.org/amqpool/2.0"> <amqpool:xa-pool id="connectionFactory" url="tcp://localhost:61616" transactionManager="#transactionManager" /> </beans> |
Take a look at the AMQPool documentation from the Jencks project for more information.
...