In camel we have a rule that message header can override the setting of endpoint.
When consumer receives the message, it puts some headers which key is start with “rabbitmq.”. As the producer always prefer the message header setting over the endpoint setting, the producer sends the message to general.queue. Then the consumer get a new message and route it to the producer. That could explain why you saw the camel keeps sending same message to the general.queue. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On December 6, 2013 at 12:34:57 AM, muthukumara...@gmail.com (muthukumara...@gmail.com) wrote: > >Thanks Willem for the quick response. > >Your suggestion resolved my issue. Can you please explain why this issue >happened and how this fixed it? > >Thanks, >Muthu > > > >-- >View this message in context: >http://camel.465427.n5.nabble.com/camel-rabbitmq-routing-issue-tp5744371p5744374.html >Sent from the Camel - Users mailing list archive at Nabble.com. >
