Question about logging message consumption errors. about messenger-enqueue-transport

[shulard]

Actually, this seems to be fixed by using the PropertyNormalizer in my Symfony services configuration.

    # Enable PropertyNormalizer on the serializer component
    # This is used inside the message transport process to serialize messages.
    serialize.property_normalize:
        class: Symfony\Component\Serializer\Normalizer\PropertyNormalizer
        public: false
        tags: [serializer.normalizer]

I close the issue here, maybe I'm not too familiar with the used components here.

[sroze]

The successes and/or exceptions should be logged for you by Symfony's Logging middleware. If you prefer another type of logging, you can simply create your own middleware.

Is this enough for your requirements? :)

[shulard]

I though that the middleware only come to the party when the application dispatch the message (everything is logged at that time).

My problem here is that I can't receive exceptions when the message is consumed by the messenger:consume-messages command. Are the middlewares active here too ?

Actually most of the errors that I miss come from the decoding process. For example if the serialized version of the object can't be decoded, the message is dropped without any notice.

Maybe I miss something here 😄.