Thanks for the response, Matt. I don't believe that's my problem because after the processor is done, I have a log statement in the Blueprint XML that shows the header has been properly set. The problem seems to be that somewhere in the processing that happens to the message in sending it to the queue, the headers are either wiped out or ignored.
Interestingly, if I use the Amazon AWS java SDK, as shown on this page <http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/SQSMessageAttributes.html> , by creating a Map<String, MessageAttributeValue> and then manually using a SendMessageRequest, it actually works. My problem with that is part of the reason for using the Camel API is that it abstracts a lot of the manual stuff for you - for instance, if I use that method I think I have to send a DeleteMessageRequest to the queue that my message originated from, or the error route will continue to receive the same message over and over. As far as I can tell, no header filtering is occurring. I read a response on another Camel User question that indicated that there would be a WARN message in the logs somewhere if headers were being filtered. Everything I read says that it should be a simple as doing what I am already attempting, so why are the headers not being honored on the receiving end of these messages? Still confused! Sean -- View this message in context: http://camel.465427.n5.nabble.com/CamelAwsSqsMessageAttributes-header-not-appearing-on-messages-in-AWS-SQS-Queue-Camel-2-15-2-tp5771992p5772058.html Sent from the Camel - Users mailing list archive at Nabble.com.
