You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2019/08/06 15:06:00 UTC

[jira] [Updated] (CAMEL-12876) camel-jms - Support transactional concurrent SimpleMessageListenerContainer

     [ https://issues.apache.org/jira/browse/CAMEL-12876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-12876:
--------------------------------
    Summary: camel-jms - Support transactional concurrent SimpleMessageListenerContainer  (was: Support transactional concurrent SimpleMessageListenerContainer)

> camel-jms - Support transactional concurrent SimpleMessageListenerContainer
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-12876
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12876
>             Project: Camel
>          Issue Type: Improvement
>          Components: came-jms
>    Affects Versions: 2.22.1
>            Reporter: James Huang
>            Priority: Major
>
> 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.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)