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
The nats.client <1.1.4 has sometimes an issue to connect to a server with "Authentication Timeout" exception.
This happens sometimes on vs debug sessions on windows or docker-desktop and in production under k8s
with dotnet 6 and 8. The nats server has an auth timeout of 5s.
With an new aspnet project in production that triggered this issue not only sometimes,
but always at startup in k8s
The nats.client requires real-concurrency (2+ cores) to connect.
A cpu limit env. like docker run --cpus=1 will trigger the lock
after the UserSignatureEventHandler call
Expected behavior
the connection should succeed with cpu limit of 1
Server and client version
nats.client 1.1.4
Host environment
windows and docker
dotnet 6 & 8
Steps to reproduce
set cpu limit to 1 in docker or resources.limits.cpu: 500m in kubernetes
The text was updated successfully, but these errors were encountered:
Observed behavior
The nats.client <1.1.4 has sometimes an issue to connect to a server with "Authentication Timeout" exception.
This happens sometimes on vs debug sessions on windows or docker-desktop and in production under k8s
with dotnet 6 and 8. The nats server has an auth timeout of 5s.
With an new aspnet project in production that triggered this issue not only sometimes,
but always at startup in k8s
The nats.client requires real-concurrency (2+ cores) to connect.
A cpu limit env. like
docker run --cpus=1
will trigger the lockafter the
UserSignatureEventHandler
callExpected behavior
the connection should succeed with cpu limit of 1
Server and client version
nats.client 1.1.4
Host environment
windows and docker
dotnet 6 & 8
Steps to reproduce
set cpu limit to 1 in docker or resources.limits.cpu: 500m in kubernetes
The text was updated successfully, but these errors were encountered: