[CXF-6195] JMS soap listeners are single-threaded in CXF 3.0.x

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.0.3
• Fix Version/s: 3.0.4, 3.1
• Component/s: JMS

Environment

Tomcat, Tibco EMS, ActiveMQ

• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: EasternWahoo
• Created: 14/Jan/15 21:57
• Updated: 27/Jan/15 13:41
• Resolved: 27/Jan/15 13:41

Description

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.

Issue Links

• duplicates: CXF-6199 Allow scalability for slow services on jms