activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nauman73 <nauma...@hotmail.com>
Subject Re: Advisory messages for remote broker clients?
Date Wed, 16 Jul 2014 07:55:53 GMT
Hi ceposta

I am having little problem with routing of advisory messages to opposite
broker. While the advisory message does appear to get routed to opposite
broker, the format of the advisory message is not the same as the original
message. The route declaration is as follows. I have followed the example
given at "Consuming Advisory Messages" section of 
http://camel.apache.org/activemq.html
<http://camel.apache.org/activemq.html>   with some modification.

<route>
<description>Connection Advisory Route</description>
<from
uri="activemq:topic:ActiveMQ.Advisory.Connection?mapJmsMessage=false"/>
<to uri="activemqRemote:topic:ActiveMQ.Advisory.Routed"/>
</route>

The issue I have is that the "dataStructure" of the routed ActiveMQMessage
is always null. Whereas the "dataStructure" of the original advisory message
has the RemoveInfo, ProducerInfo etc. depending on type of activity. If I
run the example route given at above mentioned URL, I do get the proper
"dataStructure" written to the output file used in that example.

If I change my route to match the route given in the example, except for the
"to" endpoint, the route becomes as follows.

<route>
<description>Connection Advisory Route</description>
<from
uri="activemq:topic:ActiveMQ.Advisory.Connection?mapJmsMessage=false"/>
<convertBodyTo type="java.lang.String"/>
<transform>
  <simple>${in.body}&#13;</simple>
</transform>
<to uri="activemqRemote:topic:ActiveMQ.Advisory.Camel"/>
</route>

With this route, the routed message type is changed to "ActiveMQTextMessage"
instead of the "ActiveMQMessage". The "dataStructure" is still null.

I have tried variations of above route definition. I have also tried to set
the "jmsMessageType" and "mapJmsMessage" options differently. None of these
works and I always get the dataStructure as null in the advisory message
routed to opposite broker.

Any clues?

Thanks

Regards
Nauman



--
View this message in context: http://activemq.2283324.n4.nabble.com/Advisory-messages-for-remote-broker-clients-tp4683016p4683308.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Mime
View raw message