[CAMEL-12876] camel-jms - Support transactional concurrent SimpleMessageListenerContainer

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Auto Closed
• Affects Version/s: 2.22.1
• Fix Version/s: Future
• Component/s: came-jms
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: James Huang
• Created: 12/Oct/18 06:04
• Updated: 09/Jan/22 10:59
• Resolved: 09/Jan/22 10:59

Description

I wish to use SimpleMessageListenerContainer in transacted mode with multiple consumers. 

But org.apache.camel.component.jms.JmsEndpoint line 224 is giving the listenerContainer a custom TaskExecutor, causing SimpleMessageListenerContainer to fail if sessionTransacted=true and concurrentConsumers>1. The custom taskExecutor causes JMS session commit to be called by the wrong thread randomly and fails.

Can we update JmsEndpoint to not set taskExecutor just for SimpleMessageListenerContainer? I've tested this by overriding the lib and it works well with sessionTransacted=true and concurrentConsumers>1 (Solace broker). SimpleMessageListenerContainer has many benefits like true event driven over the default polling listenerContainer. Will be great to get it properly supported.