No Parallel Processing when using Transacted=true in camel jms

Solution Unverified - Updated -

Issue

  • We created a route and in order to dequeue messages in parallel, defined 5 consumers.

    • When transacted=false, everyhing is OK and messages are dequeued in parallel.
    • When transacted=true, route reads the first message from a message group, waits for its completion and then dispatch the other messages to the consumers. If new messages arrives, they're waiting for the completion of the first message group before to be dispatch to consumers.
  • Can you explain this behaviour when transacted=true ? What is the exact behaviour of this parameter ? When should I set it to true ?

Environment

  • Red Hat JBoss Fuse
    • 6.x
  • Apache Camel

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.