New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spring Cloud produced messages fail parsing #46
Comments
Are you setting any non-String attributes on the message? (I suspect that might happen in |
Hi Adam, |
I had the same issue. Spring Cloud uses spring-messaging which automatically adds UUID (string) and timestamp(long) to a message's headers. And those headers will be transformed into SQS message attributes. Timestamp causes this issue. As a workaround you can override doSend method in QueueMessagingTemplate and remove timestamp header from the message. |
I think adding support for all message attribute types shouldn't be too hard, if somebody would like to attempt a PR :) |
It wasn't ) I am currently working on it. Just need to write some more tests for SQSStrict mode to check that number attribute's value is inside -10^128 .. 10^126. So expect PR really soon ) |
Awesome! :) |
Issue #46. Spring Cloud produced messages fail parsing. Support Number MessageAttributes
Merged & released 0.8.10 - thanks! |
I'm trying to use an embedded elasticmq in my Spring Boot/Spring Cloud application but getting exceptions when sending a message:
I originally thought that it was Spring incorrectly creating the message, which elasticMq was then failing to process, however, when running the same code against a real SQS service, both sending and receiving messages works.
My project code looks like this:
The text was updated successfully, but these errors were encountered: