NATS Go ConnPool exhaustion returns ErrPoolEmpty immediately without blocking option
Connection pool exhaustion behavior The NATS Go client's ConnPool feature enforces a hard MaxConnections limit. When all pooled connections are in use, NextConnection returns ErrPoolEmpty without blocking the caller. The documented API does not expose a wait or timeout parameter that would allow a caller to queue until a connection becomes available. Version
nats