camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Commented: (CAMEL-1689) JMS-Headers are ignored in Producer
Date Wed, 01 Jul 2009 08:24:07 GMT


Claus Ibsen commented on CAMEL-1689:

JMSDestination is *not* possible to set in a IN header as it can cause jms routing to go into
looping such as:


In this case when we receive a message from *foo* then it will populate a Camel message that
contains the details from the javax.jms.Message and thus also {{JMSDestination}}.
And it will be {{queue://foo}}. So when the message is routed to the {{to}} endpoint then
it will mistakenly send it back to itself, instead of using the {{queue:bar}} destination
defined on the endpoint.

> JMS-Headers are ignored in Producer
> -----------------------------------
>                 Key: CAMEL-1689
>                 URL:
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-jms
>    Affects Versions: 2.0-M1
>            Reporter: Siegfried Wirth
>            Assignee: Claus Ibsen
>             Fix For: 2.0.0
> Camel jms producer ignores some JMSHeaders. For example the header JMSPriority is ignored
- due to the comment in the code, because it is set by the producer. But it should not only
be set by the produer due to the received message, it should also be possible to set a priority
using the JMSPriority header on the consumer. (See also the option preserveMessageQos on the
jms endpoint - if every JMSHeader is ignored by the producer it is impossible to set Qos-Properties
on the message.)
> The reason for the bug is in org.apache.camel.component.jms.JmsBinding#appendJmsProperty.

> The follwoing JMS message headers are useful for sending messages and therefore should
be copied to the jms message:
> - JMSDestination
> - JMSDeliveryMode
> - JMSExpiration
> - JMSPriority
> - JMSMessageID
> - JMSTimestamp

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

View raw message