Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

[Messenger] SF 4.3 RedeliveryStamp requires not null $senderClassOrAlias #31231

Copy link
Copy link
Closed
@raress96

Description

@raress96
Issue body actions

Symfony version(s) affected: 4.3

Description
The RedeliveryStamp, used for handling retrying of messages, requires in the constructor the $senderClassOrAlias argument.
However, in the Worker.php class, on line 148, a new instance of the object is created, and the $senderClassOrAlias argument can be null according to the code there, so the application crashes when trying to handle a message whose handler returned an error.

How to reproduce
Publish a message to a queue. Try to handle that message but return an exception in the handler. Notice the exception.

Possible Solution
Allow $senderClassOrAlias argument to be null.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.