You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "William Tam (JIRA)" <ji...@apache.org> on 2008/12/09 08:24:05 UTC
[jira] Resolved: (CAMEL-1037) Messages in Resequencer between 2 JMS
queues get stuck
[ https://issues.apache.org/activemq/browse/CAMEL-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William Tam resolved CAMEL-1037.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
1.5.1
Committed revision 724629 to camel-1.x.
Committed revision 724619 to trunk
> Messages in Resequencer between 2 JMS queues get stuck
> ------------------------------------------------------
>
> Key: CAMEL-1037
> URL: https://issues.apache.org/activemq/browse/CAMEL-1037
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 1.5.0
> Reporter: Jonathan Anstey
> Assignee: William Tam
> Fix For: 1.5.1, 2.0.0
>
> Attachments: camel-1.x.patch, camel-2.0.patch
>
>
> Martin describes the issue as follows in CAMEL-1034:
> "The issue with the regular resequencer (the one that extends the BatchProcessor) remains because the process(Exchange) method is empty. In addition to the BatchProcessor's polling consumer, an additional JmsConsumer is created by the JMS endpoint that competes with the polling consumer. The JmsConsumer then calls the empty process(Exchange) method and the exchange is lost."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.