[
https://issues.apache.org/jira/browse/CXF-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290516#comment-14290516
]
Erwin Oldenkamp edited comment on CXF-6195 at 1/24/15 10:29 AM:
----------------------------------------------------------------
I believe this is a duplicate for https://issues.apache.org/jira/browse/CXF-6199
was (Author: eernie):
I believe this is an duplicate for
https://issues.apache.org/jira/browse/CXF-6199
> JMS soap listeners are single-threaded in CXF 3.0.x
> ---------------------------------------------------
>
> Key: CXF-6195
> URL: https://issues.apache.org/jira/browse/CXF-6195
> Project: CXF
> Issue Type: Bug
> Components: JMS
> Affects Versions: 3.0.3
> Environment: Tomcat, Tibco EMS, ActiveMQ
> Reporter: EasternWahoo
>
> CXF 2.x delegated to Spring's DefaultMessageListenerContainer, and provided a
> mechanism for configuring concurrent and maximum threads. This capability was
> removed in CXF 3.0, and the listeners are now single-threaded. This prevents
> use of CXF in production. Some of the CXF 3.0 classes seem to be set up to
> support multi-threading, but are hard-coded to use single threading in 3.0.3:
> MessageListenerContainer contains a DispachingListener which appears capable
> of multi-threading via an Executor, but its start() method uses
> LocalTransactionMessageListener instead.
> PollingMessageListenerContainer has a hard-coded numListenerThreads, set to
> 1. There is no setter for this property.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
