activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <>
Subject Re: Resequencing with Camel
Date Wed, 24 Feb 2010 10:38:04 GMT
you may have more luck with a useful reply on the camel users forum.
One thought, are you sure the header property is present?. Could it be
"in.header.JMSPriority" (with a capital 'P')? Possibly try using a property
that you explicitly set on the original message, just the be sure the naming
and referencing is correct?

On 24 February 2010 02:01, Andrew Harvey <> wrote:

> Hi there,
> I'm having some trouble resequencing some queues with camel, but it's not
> working and I'm stumped as to why. Camel will happily route messages between
> queues, but the resequencer just doesn't seem to want to go.
> Here is the configuration I have for camel:
>      <camelContext id="camel" xmlns="
> ">
>            <route autoStartup="true">
>              <from uri="activemq:queue:AnalysisIn" />
>              <resequencer>
>                <simple>in.header.JMSpriority</simple>
>                <to uri="activemq:queue:AnalysisOut" />
>                <batch-config batchSize="20" batchTimeout="4000" />
>              </resequencer>
>            </route>
>        </camelContext>
> Can anyone shed any light on why this might not be working? I'm at a bit of
> a loss. I'm sure its something simple, but I just can't see it.
> Thanks,
> Andrew
> Andrew Harvey / Developer
> lexer
> m/
> t/ +61 2 9019 6379
> w/
> Please consider the environment before printing this email
> This email transmission is confidential and intended solely for the person
> or organisation to whom it is addressed. If you are not the intended
> recipient, you must not copy, distribute or disseminate the information, or
> take any action in relation to it and please delete this e-mail. Any views
> expressed in this message are those of the individual sender, except where
> the send specifically states them to be the views of any organisation or
> employer. If you have received this message in error, do not open any
> attachment but please notify the sender (above). This message has been
> checked for all known viruses powered by McAfee.
> For further information visit
> Please rely on your own virus check as no responsibility is taken by the
> sender for any damage rising out of any virus infection this communication
> may contain.
> This message has been scanned for malware by Websense.


Open Source Integration

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message