Skip to content

Channel connection is closed,how to reproduce this bug #600

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.

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

Open
gitdreamer01 opened this issue Sep 9, 2024 · 1 comment
Open

Channel connection is closed,how to reproduce this bug #600

gitdreamer01 opened this issue Sep 9, 2024 · 1 comment
Assignees

Comments

@gitdreamer01
Copy link

gitdreamer01 commented Sep 9, 2024

  • Laravel/Lumen version: Laravel 6.0
  • RabbitMQ version: 3
  • Package version: v10.1.0

Describe the bug

image
image

Steps To Reproduce

What steps needed, to reproduce this bug.

Current behavior

  • What happens with the worker?
  • Is the message retried or put back into the queue?
  • Is the message acknowledged or rejected?
  • Is the message unacked?
  • Is the message gone?

Expected behavior

What is the expected behavior

Additional context

Add any other context about the problem or describe the use-case.

@gitdreamer01 gitdreamer01 changed the title Channel connection is closed Channel connection is closed,how to reproduce this bug Sep 9, 2024
@fontebasso
Copy link
Contributor

Thanks for reporting, @gitdreamer01.

Version 10.1.0 of this package, which you're using, officially reached end-of-support on September 3rd, 2021. You can confirm this in the v10.1.0 release documentation.

Since this version is no longer maintained, and the issue appears to be related to its limitations, I believe this issue can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants