activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pete Schwamb (JIRA)" <j...@apache.org>
Subject [jira] Created: (AMQ-1620) compositeTopic changing destination field of original message
Date Thu, 13 Mar 2008 21:02:32 GMT
compositeTopic changing destination field of original message
-------------------------------------------------------------

                 Key: AMQ-1620
                 URL: https://issues.apache.org/activemq/browse/AMQ-1620
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.1.0
            Reporter: Pete Schwamb
         Attachments: composite_destination_filter_patch.txt

 When using compositeTopics to copy messages from one destination to multiple queues or topics,
and setting forwardOnly="false", messages sent out on the original topic will have the destination
field set to the last forwarded topic/queue name.  For example, using this config:

<compositeTopic name="original.topic" forwardOnly="false">
    <forwardTo>
        <queue physicalName="forwarded.queue" />
        <topic physicalName="forwarded.topic" />
    </forwardTo>
</compositeTopic>

Messages sent out on the original.topic topic will have "forwarded.topic" set as their destination.

My stomp client (activemessaging) uses the destination field to route messages locally after
they are received, so this causes big problems for me.

I have attached a patch that fixes this behavior.


-- 
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