[
https://issues.apache.org/jira/browse/CAMEL-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Watkins updated CAMEL-3938:
----------------------------------
Patch Info: [Patch Available]
Affects Version/s: 2.7.3
2.8.0
> Re-add support for ComsumerType.Simple/JMS SimpleMessageListenerContainer
> -------------------------------------------------------------------------
>
> Key: CAMEL-3938
> URL: https://issues.apache.org/jira/browse/CAMEL-3938
> Project: Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 2.7.0, 2.7.3, 2.8.0
> Reporter: Joshua Watkins
> Attachments: simpleMessageListenerContainerAddition
>
>
> A while ago there was a discussion topic that the
> SimpleMessageListenerContainer/ConsumerType.Simple was removed from
> camel-jms as it was deprecated. However from looking at the latest Spring
> docs (
> http://static.springsource.org/spring/docs/3.1.0.M1/javadoc-api/org/springf
> ramework/jms/listener/SimpleMessageListenerContainer.html ) it is alive
> and kicking.
> Is there another reason that this feature was removed?
> The reason I am so keen on the SimpleMessageListenerContainer is that the
> DefaultMessageListenerContainer does not allow you to constrain the number
> of threads used in a useful way. If you give it a task executor with a
> maximum 5 threads and want to listen on 10 routes, only 5 of those routes
> would be consumed from. There is even a note about this fact in the docs (
> http://static.springsource.org/spring/docs/3.1.0.M1/javadoc-api/org/springf
> ramework/jms/listener/DefaultMessageListenerContainer.html#setTaskExecutor(
> java.util.concurrent.Executor) ). This makes the
> SimpleMessageListenerContainer invaluable for scaling out an application
> using camel-jms.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
