Spring Cloud produced messages fail parsing about elasticmq HOT 7 CLOSED

Are you setting any non-String attributes on the message? (I suspect that might happen in queueMessagingTemplate.convertAndSend) Currently only String-typed attributes are supported

from elasticmq.

Hi Adam,
I am passing JSON message and facing the same issue. Is there any plan in near future to provide support for JSON type ?

from elasticmq.

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.

from elasticmq.

I think adding support for all message attribute types shouldn't be too hard, if somebody would like to attempt a PR :)

from elasticmq.

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 )

from elasticmq.

Awesome! :)

from elasticmq.

Merged & released 0.8.10 - thanks!

from elasticmq.