Skip to content

Navigation Menu

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

STOMP: "Was not possible to write frame!" causing zombie connections #1097

Copy link
Copy link
Closed
@atrauzzi

Description

@atrauzzi
Issue body actions

I'm able to somewhat reliably reproduce a situation where my queue worker in Laravel ends up no longer able to successfully connect to a broker. It takes a few consecutive jobs before it happens, but eventually my one queue gets the exception "Was not possible to write frame!".

Thereafter, any attempt to send messages to the same broker end up reporting the same exception. It seems like the connection becomes corrupted here and no recovery is attempted by enqueue or the stomp-php library itself.

Is there any general advice on how to handle this or is this something that enqueue can catch and recreate its connection?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    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.