[
https://issues.apache.org/activemq/browse/CAMEL-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56689#action_56689
]
Dragisa Krsmanovic commented on CAMEL-2305:
-------------------------------------------
Setting prefetch to 0 is not ideal because it can impact performance. Allowing
to set consumer prefetch size as an option in AMQ component url would, at
least, allow us to still use prefetch in other routes that do not use polling
consumer.
> Polling consumer does not work well with transacted ActiveMQ 5.3.0
> ------------------------------------------------------------------
>
> Key: CAMEL-2305
> URL: https://issues.apache.org/activemq/browse/CAMEL-2305
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-jms
> Affects Versions: 2.0.0, 2.1.0, 2.2.0
> Reporter: Dragisa Krsmanovic
> Attachments: JmsPollingConsumerTest.patch
>
>
> A bean in a activemq route is consuming messages from another activemq queue.
> Instead of reading all queued messages, it always gets just the first
> message in the queue.
> {code:java}
> while ((exchange = consumer.receive("activemq:queue", 2000l)) != null) {
> ...
> }
> {code}
> * This did not happen with ActiveMQ 5.2.0
> * This does not happen if Spring transaction support is not set for activemq
> component.
> * This does not happen if consumer bean is invoked from direct: route.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
