How to configure asynchronous processing of incoming JMS messages

[Andreas Vallen <an...@gmail.com>]

Hi,

I am surprised to find that a CXF SOAP endpoint configured with the JMS
transport does not process those messages asynchronously.

Instead the configured number of concurrentConsumers is the effective limit
of concurrent messages that are processed concurrently.

I wonder if this is by design or if I am missing some configuration that
allows the consumers to asynchronously dispatch incoming messages, freeing
them to consume additional messages, while message processing could be
scheduled by some independently configured thread-pool.

Kind Regards,
Andreas