We have an Activemq Cluster of 3 brokers (Master - Master, multicast) with 2 networkConnectors (for each broker with duplex turned on) with one connector for queues with conduitSubscriptions as false and the other connector for topics with conduitSubscriptions as true. Activemq version is 5.6 and Camel is 2.10.1. Even with this configuration, I have situations during my testing where I have a consumer with a selector which does not seem to receive a message even though the message is is available on a remote broker. Sometimes it works and sometimes it does not and I am unable to figure a pattern. For the consumer, I am using the ConsumerTemplate class and the receive method. With one broker, everything works fine.
Just to be more clear, the consumer is already waiting on the queue (only 1 consumer) before I send the messages. Subsequently, I send a large number of messages with a small number of them containing the header matching the selector. It would be great if someone could point out if I am missing something obvious. -- View this message in context: http://camel.465427.n5.nabble.com/JMS-Selectors-and-Activemq-Cluster-tp5721615.html Sent from the Camel - Users mailing list archive at Nabble.com.
