You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cxf.apache.org by "EasternWahoo (JIRA)" <ji...@apache.org> on 2015/01/14 22:58:34 UTC

[jira] [Created] (CXF-6195) JMS soap listeners are single-threaded in CXF 3.0.x

EasternWahoo created CXF-6195:
---------------------------------

             Summary: 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)