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
{{ message }}
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.
We have containers running in ACI. Containers internally open TCP connections to several services (2-4 services) per container. For example, there is a container C1, which opens outgoing connection to Service1 and Service2.
On the beginning all works fine. Depending on application state, container C1 get after few hours timeout exception to Service1 or Service2 or both. It looks as both services wouldn't be reachable.
However services are reachable. As example, one of services is IotHub. At the moment of error, both services can be reached from another application, which is not running in ACI.
After restarting of container all works for next few hours. When we run same application locally (not as container) all works fine.
Container is setup for 1.5GB RAM and application is performing as shown in picture below:
Question
Is it possible, that ACI containers have some limitation related to outbound connections, similar to WebJob containers?
Thanks.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have containers running in ACI. Containers internally open TCP connections to several services (2-4 services) per container. For example, there is a container C1, which opens outgoing connection to Service1 and Service2.
On the beginning all works fine. Depending on application state, container C1 get after few hours timeout exception to Service1 or Service2 or both. It looks as both services wouldn't be reachable.
However services are reachable. As example, one of services is IotHub. At the moment of error, both services can be reached from another application, which is not running in ACI.
After restarting of container all works for next few hours. When we run same application locally (not as container) all works fine.
Container is setup for 1.5GB RAM and application is performing as shown in picture below:
Question
Is it possible, that ACI containers have some limitation related to outbound connections, similar to WebJob containers?
Thanks.
The text was updated successfully, but these errors were encountered: