camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Anstey (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-1034) Messages in StreamResequencer between 2 ActiveMQ queues seem to be stuck
Date Thu, 30 Oct 2008 15:09:05 GMT

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

Jonathan Anstey resolved CAMEL-1034.
------------------------------------

    Fix Version/s: 2.0.0
       Resolution: Fixed

> Messages in StreamResequencer between 2 ActiveMQ queues seem to be stuck
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-1034
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1034
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.4.0
>         Environment: Windows XP SP3, Sun JDK 1.5.0_11, FUSE Mediation Router 1.4.5, ActiveMQ
5.1.0.1
>            Reporter: Peter MacKinnon
>            Assignee: Jonathan Anstey
>             Fix For: 2.0.0
>
>         Attachments: camel-core.patch, stream-resequencer-eclipse-test.zip, stream-resequencer-trace.txt
>
>
> Perhaps some subtle configuration issue, but a Camel stream resequencer that is a route
between 2 ActiveMQ queues fails to deliver all ordered messages. In fact, using the defaults
for a StreamResequencer only 1 out of 100 messages are delivered. However, all 100 messages
have been removed from the Producer queue by the resequencer and are not moved to the consumer
queue either (even unordered). 
> Relevant points:
> - Broker is run external to Camel route (non-embedded, no VM transport)
> - Producer is a Camel ProducerTemplate
> - Consumer is a Camel route that listens on another delivery queue and delivers message
to a simple stdout Processor
> - Resequencer uses stream defaults (100, 1000ms)
> - Trace warns of some Converter override (see attached trace) and throws a breadcrumb
error
> - Resequencer fails delivery whether using body (long) or seqnum header (long)
> - all JMS components are configured for AutoAcks

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message