symfony: [Messenger] ErrorDetailsStamp +RedeliveryStamp can lead to an oversize message for SQS

Just in case anyone needs a workaround: https://github.com/mtanasiewicz/symfony-messenger-sqs-workaround

With rabbitmq and the amqp PHP library, the header limit is even just 128 KB (overall, not per header). I adjusted our application to remove the error details stamp alltogether (which would not be a good general solution of course). How about a configuration for the allowed header size (that maybe could be default to the correct value if known?) and in addition to reduce verbosity of the stack trace also shorten the trace to strictly prevent errors even on very deep traces with long namespaces?

its tricky that the limit is overall. maybe serialize everything, then check the length and if it is too long shorten the error details by the difference + 100 bytes of safety margin?

btw: i am surprised that the amqp library allows to send messages that break the system, they could check the header limit on sending as well and not only on receiving…

I have same problem while using SQS. I cheched stack trace and main problem for oversized messages is, that arguments of functions are serialized too.

aws/aws-sdk-php package contains more functions, that receives whole serialized message as string. If those functions are called 4 times in one run and after retry 4 more times, size of the envelope grows exponentially.

I can think of one solution: You can override Symfony\Component\Messenger\EventListener\AddErrorDetailsStampListener and create custom Symfony\Component\Messenger\Stamp\ErrorDetailsStamp with exception without function argumets. This can downsize message drastically.

It is only a theory, I must try it. With this solution you lose function arguments in stack trace, but better than oversized message.