PHPackages                             recranet/messenger-amqp-decorated - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Queues &amp; Workers](/categories/queues)
4. /
5. recranet/messenger-amqp-decorated

ActiveSymfony-bundle[Queues &amp; Workers](/categories/queues)

recranet/messenger-amqp-decorated
=================================

Transport decorator that removes ErrorDetailsStamp before sending messages to AMQP

1.0.0(4mo ago)07MITPHPPHP &gt;=8.2

Since Dec 22Pushed 4mo agoCompare

[ Source](https://github.com/recranet/messenger-amqp-decorated)[ Packagist](https://packagist.org/packages/recranet/messenger-amqp-decorated)[ RSS](/packages/recranet-messenger-amqp-decorated/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (1)Dependencies (3)Versions (2)Used By (0)

Messenger AMQP Decorated
========================

[](#messenger-amqp-decorated)

Transport decorator that removes `ErrorDetailsStamp` and `RedeliveryStamp` before sending messages to AMQP.

Problem Solved
--------------

[](#problem-solved)

When Symfony Messenger retries failed messages, it adds stamps containing:

- `ErrorDetailsStamp`: Exception class name, message, and full stack trace
- `RedeliveryStamp`: Retry metadata with exception details

On each retry, **new stamps are added**, causing accumulation. After several retries, the AMQP headers become too large, resulting in:

- "Invalid AMQP data" errors
- "table too large for buffer" errors

Solution
--------

[](#solution)

This decorator wraps AMQP transports and strips `ErrorDetailsStamp` and `RedeliveryStamp` before `send()`, keeping messages within AMQP header limits.

Are Failed Messages Still Retried?
----------------------------------

[](#are-failed-messages-still-retried)

**Yes.** Both `ErrorDetailsStamp` and `RedeliveryStamp` are purely informational/diagnostic - they don't control retry behavior.

The retry mechanism is controlled by:

- `DelayStamp` - controls retry delay timing
- Retry count and strategy from `messenger.yaml` config

These are **not** removed by this decorator.

Flow
----

[](#flow)

1. Message fails -&gt; `ErrorDetailsStamp` and `RedeliveryStamp` added (in memory)
2. Retry logic kicks in (based on retry strategy)
3. `send()` called -&gt; **stamps removed** by this decorator
4. Message sent to AMQP without large headers
5. Worker picks it up, retries execution
6. If fails again -&gt; new stamps added -&gt; cycle repeats

Trade-off
---------

[](#trade-off)

You lose error details history in the message headers, but the messages continue to retry correctly.

Installation
------------

[](#installation)

```
composer require recranet/messenger-amqp-decorated
```

If you're using Symfony Flex, the bundle is registered automatically.

Otherwise, add it to `config/bundles.php`:

```
return [
    // ...
    Recranet\MessengerAmqpDecorated\MessengerAmqpDecoratedBundle::class => ['all' => true],
];
```

Usage
-----

[](#usage)

No configuration needed. The bundle automatically decorates `messenger.transport.amqp.factory`, wrapping all AMQP transports.

###  Health Score

35

—

LowBetter than 79% of packages

Maintenance74

Regular maintenance activity

Popularity4

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity47

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Unknown

Total

1

Last Release

142d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/bdd6d6951efb85c875a00f2ff0e04c4be6bfc2d5943d37cdafd510cd68d3878b?d=identicon)[recranet](/maintainers/recranet)

---

Top Contributors

[![mikepage](https://avatars.githubusercontent.com/u/17899539?v=4)](https://github.com/mikepage "mikepage (8 commits)")

### Embed Badge

![Health badge](/badges/recranet-messenger-amqp-decorated/health.svg)

```
[![Health](https://phpackages.com/badges/recranet-messenger-amqp-decorated/health.svg)](https://phpackages.com/packages/recranet-messenger-amqp-decorated)
```

###  Alternatives

[sylius/sylius

E-Commerce platform for PHP, based on Symfony framework.

8.4k5.6M651](/packages/sylius-sylius)[shopware/platform

The Shopware e-commerce core

3.3k1.5M3](/packages/shopware-platform)[sulu/sulu

Core framework that implements the functionality of the Sulu content management system

1.3k1.3M152](/packages/sulu-sulu)[prestashop/prestashop

PrestaShop is an Open Source e-commerce platform, committed to providing the best shopping cart experience for both merchants and customers.

9.0k15.4k](/packages/prestashop-prestashop)[shopware/storefront

Storefront for Shopware

684.2M148](/packages/shopware-storefront)[shopware/core

Shopware platform is the core for all Shopware ecommerce products.

595.2M386](/packages/shopware-core)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
