Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-6195

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

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 3.0.3
    • 3.0.4, 3.1
    • JMS
    • None
    • Tomcat, Tibco EMS, ActiveMQ

    • Unknown

    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.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              easternwahoo EasternWahoo
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: