8000 Messenger retry fails on AMQP with "table too large for buffer" error · Issue #60370 · symfony/symfony · GitHub
[go: up one dir, main page]
Skip to content

Messenger retry fails on AMQP with "table too large for buffer" error #60370

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.

Sign up for GitHub

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

Jump to bottom
Open
Jean85 opened this issue May 7, 2025 · 2 comments
Open

Messenger retry fails on AMQP with "table too large for buffer" error #60370

Jean85 opened this issue May 7, 2025 · 2 comments
Labels
Bug Messenger Status: Needs Review

Comments

@Jean85
Copy link
Contributor
Jean85 commented May 7, 2025

Symfony version(s) affected

7.1.9

Description

This is a recurring issue with Messenger: when failing, stamps like ErrorDetailsStamp are added and they get to big to be accepted by the transport. In the AMQP case, you get a "table too large for buffer" error, we also had this in the past with #34082

How to reproduce

  1. dispatch a Messenger message through an AMQP (Rabbit) transport
  2. make it fail with a big stack trace

Possible Solution

I'm currently unable to properly get more details on this issue, because the retry failure is hiding the full cause. In my use case, I'm getting a 400 from an API call, but I don't know how to intercept the stamps and reduce them as a workaround/troubleshooting for this.

Additional Context

No response
@Jean85 Jean85 added the Bug label May 7, 2025
@tim-lappe
Copy link

I’ve never run into this issue myself, but it seems to be a general problem as discussed here: #44943. Some workarounds were also posted, which might help.

@Jean85
Copy link
Contributor Author
Jean85 commented May 8, 2025

Thank you for referencing that! I was already replying there too, but I couldn't find it.

Yes it's the same issue: failing messages get over the header limit of the transport, and the retry mechanism fails all together... That's bad :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Messenger Status: Needs Review
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@xabbuh @Jean85 @carsonbot @tim-lappe
0