The core JMS client sets the routing-type of the message automatically based on what kind of destination it's working with (i.e. ANYCAST for queues & MULTICAST for topics). That explains the discrepancy.
Justin On Fri, Mar 22, 2019 at 7:51 AM ldebello <[email protected]> wrote: > Sorry for the delay, > > This is a springboot project which use the jmsTemplate, I didn't debug to > check if there is some property set inside this code but the change was the > following. > > First Version: We used artemis-client (2.5.0) connecting to the following > uri tcp://localhost:5672. > Second Version: We removed artemis-client and start using qpid (0.40.0) > client connecting to the following uri: amqps://localhost:5672 > > In the first case we got a CoreMessage with routing type null and in the > second case the we got a AMQMessage with routing type ANYCAST. we didnt set > any routing type by code, but as I mentioned before I didn't debug the jms > template to confirm if maybe this adding some properties. > > Anyway adding routingtype in the divert config solve this case. > > Regards, > Luis > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
