-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Producers/Consumers etc. are not lazy #96
Comments
func0der
changed the title
Producers are not lazy
Producers/Consumers etc. are not lazy
Dec 21, 2020
Thanks for the report. Right now I am very busy these days, I'll see if I can get to it soon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey there,
I tried the lazy connections. They seem to work fine.
What is not lazy are the producers and probably the consumers either.
Given I have the AMQP (library not extension) connection set up as lazy and my producers config in the DI container (laminas in this case) looks like this:
I inject that specific producer into a class (console command in this case) and get the following error:
The line that is referenced here is the referencing the
ProducerFactory
that tries to create a new channel, even though it does not have to at creation time.When the channel is created the connection will initialize which makes the "Lazy" connection unlazy.
Am I using this feature wrong?
If not, what good is a lazy connection, if every other aspect of the library is eager? :D
Is there a plan to implement lazy producers/consumers/exchanges etc. that basically just trigger the connection if needed?
The text was updated successfully, but these errors were encountered: