You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 19, 2022. It is now read-only.
When sending a messages using the AWS QueueMessagingTemplate, a warning is logged every time:
WARN o.s.c.a.m.core.QueueMessageChannel - Message header with name 'id' and type 'java.util.UUID' cannot be sent as message attribute because it is not supported by SQS.
The issue is that the MessageHeaders always includes an id header of type UUID. I can do some magic before the Message actually reaches this point of the code, but there is no way of creating MessageHeaders without an ID.
Changing log level works, and not having the generated ID as part of the SQS message attributes is fine - but it would make sense to ignore the ID header and not log.
The text was updated successfully, but these errors were encountered:
I have this same problem. I seems like spring cloud aws should be responsible for making sure any headers generated should match what is sent to SQS without throwing warnings.
--We are still seeing this in 1.0.4.RELEASE. Was there maybe a regression?--
My issue is coming out of a similar class: org.springframework.cloud.aws.messaging.core.TopicMessageChannel
When sending a messages using the AWS
QueueMessagingTemplate
, a warning is logged every time:Logged from:
org.springframework.cloud.aws.messaging.core.QueueMessageChannel#getMessageAttributes
The issue is that the
MessageHeaders
always includes an id header of type UUID. I can do some magic before the Message actually reaches this point of the code, but there is no way of creatingMessageHeaders
without an ID.Changing log level works, and not having the generated ID as part of the SQS message attributes is fine - but it would make sense to ignore the ID header and not log.
The text was updated successfully, but these errors were encountered: