[
https://issues.apache.org/activemq/browse/CAMEL-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52678#action_52678
]
Claus Ibsen commented on CAMEL-1795:
------------------------------------
A workaround is to always use option {{maxMessagesPerTask=-1}} on all your JMS
endpoints.
> camel-jms - wrong defaults causes message listener to use new thread when
> receiving a message
> ---------------------------------------------------------------------------------------------
>
> Key: CAMEL-1795
> URL: https://issues.apache.org/activemq/browse/CAMEL-1795
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-jms
> Affects Versions: 1.6.1, 2.0-M2
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Critical
> Fix For: 1.6.2, 2.0.0
>
>
> JmsConfiguratiuon have a bad default
> maxMessagesPerTask=1
> It should be -1 as we do not want to strict the
> DefaultMessageListenerContainer to only handle 1 message per thread.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
