You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using service containers as a form of basic local up for our developers. This means that we've got a basic set of features available during either development or a local go test ./... that can use these databases.
What we've experienced is that these tests run fine once, but on the second run they cannot form a connection with the service containers. We also setup postgres, and you cannot run psql to connect to said database again.
We've found no logs in to highlight that there is a degradation in the connection.
We sadly cannot share the code explicitly because it is private, I can probably reproduce it in a minimal reproducible example if needed.
However, we basically just need to start a service container, and then in a separate process open a lot of connections to said service via. localhost, and do that over an over until the connection degrades, sometimes it takes a few attempts.
2024-04-25T09:38:24.209+0200 error transport/consumer.go:90 [amqp] Consumer Go routine stopped with an error: initialize consumer on exchange integrationevents routing keys [identity.identity.IdentityDeleted]: declare exchange 'integrationevents': Exception (504) Reason: "channel/connection is not open" {"log_type": "app", "template": "[amqp] Consumer Go routine stopped with an error: %v"}
go.lunarway.com/amqp/transport.(*Consumer).StartConsumer.func1
/Users/kah/go/pkg/mod/go.lunarway.com/[email protected]/transport/consumer.go:90
2024-04-25T09:38:24.209+0200 info transport/consumer.go:92 [amqp] Consumer Go routine stopped {"log_type": "app", "template": "[amqp] Consumer Go routine stopped"}
2024-04-25T09:38:34.208+0200 error [email protected]/logger.go:13 [vostok] Shutdown of components timed out (timeout: 10s). Exiting now! {"log_type": "app", "template": "[vostok] Shutdown of components timed out (timeout: %s). Exiting now!"}
As you can tell after a few attempts we simply cannot form the tcp connection with the rabbitmq service container. It may be because there isn't enough tcp connections available though. But I do see runs run through successfully once.
The text was updated successfully, but these errors were encountered:
What is the issue?
We're using service containers as a form of basic local up for our developers. This means that we've got a basic set of features available during either development or a local go test ./... that can use these databases.
What we've experienced is that these tests run fine once, but on the second run they cannot form a connection with the service containers. We also setup postgres, and you cannot run
psql
to connect to said database again.We've found no logs in to highlight that there is a degradation in the connection.
Dagger version
dagger v0.10.1 (registry.dagger.io/engine) darwin/arm64
Steps to reproduce
We sadly cannot share the code explicitly because it is private, I can probably reproduce it in a minimal reproducible example if needed.
However, we basically just need to start a service container, and then in a separate process open a lot of connections to said service via. localhost, and do that over an over until the connection degrades, sometimes it takes a few attempts.
Log output
We got no log output to suggest what went wrong.
service container
engine
our application
As you can tell after a few attempts we simply cannot form the tcp connection with the rabbitmq service container. It may be because there isn't enough tcp connections available though. But I do see runs run through successfully once.
The text was updated successfully, but these errors were encountered: