[
https://issues.apache.org/jira/browse/CXF-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282824#comment-14282824
]
Christian Schneider commented on CXF-6199:
------------------------------------------
You can use the JMSConfigFeature but you can also use the new URI based config
like shown here:
https://fisheye6.atlassian.com/browse/cxf/rt/transports/jms/src/test/java/org/apache/cxf/transport/jms/uri/JMSEndpointTest.java?r1=41f3f6beb5b090ff72a9cf19b0b1d1d23986f5cd&r2=642cf8dd0ade538995be3d5cfd90bdd3c5df3f36&u=3
> Allow scalability for slow services on jms
> ------------------------------------------
>
> Key: CXF-6199
> URL: https://issues.apache.org/jira/browse/CXF-6199
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 3.0.3
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 3.1.0
>
>
> Currently the CXF transport does not scale well if the service implementation
> is slow.
> We need a facility to work with several threads.
> There are two options for this:
> 1. Allow to use more than one consumer
> 2. Use an executor in JMSDestination.onMessage
> Option 1 works well with PollingMessageListener but not with the event driven
> MessageListener. It is also depending on the JMS provider how it scales with
> number of consumers.
> Option 2 works in all cases but does not allow to profit from more than one
> consumer if the provider is slow with a single consumer.
> So probably we will need both variants.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
