Closed artem-webdev closed 3 years ago
@artem-webdev This behavior is expected: the original connection is not closed/lost, you just try to create a new connection with the same client ID, which the server will reject because it can reach the first one (will send an heartbeat and get a response). Had it be 2 different processes and the first would have exited, then reusing the same client ID would work. https://docs.nats.io/nats-streaming-concepts/client-connections
there is such a code in a real project clientId cannot be changed !!! how can I reconnect if I get in response - stan: clientID already registered ?