connect trace does not log server uri when reconnecting

[hoodaajay1]

When we connect to nats initially the trace shows the server UI

[07:01:00.298] connect trace: creating connection object
[07:01:00.324] connect trace: creating executors
[07:01:00.325] connect trace: creating reader and writer
[07:01:00.33] connect trace: connection object created
[07:01:00.33] connect trace: starting connect loop
[07:01:00.331] connect trace: setting status to connecting
[07:01:00.331] connect trace: trying to connect to nats://localhost:4222
[07:01:00.331] connect trace: starting connection attempt, 30.000 (s) remaining
[07:01:00.332] connect trace: waiting for reader, 29.999 (s) remaining

However when it tries to reconnect the URI is not logged which is not helpful as if we have different nats servers to connect to & one of them has a problem its tough to find out.

Changing line 357 in NatsCOnnection.java to will fix it.
timeCheck(trace, end, "starting connection attempt to " + serverURI);

[07:02:26.735] connect trace: starting connection attempt, 30.000 (s) remaining
[07:02:26.736] connect trace: waiting for reader, 29.999 (s) remaining
[07:02:26.736] connect trace: waiting for writer, 29.999 (s) remaining
[07:02:26.736] connect trace: cleaning pong queue, 29.999 (s) remaining
[07:02:26.737] connect trace: connecting data port, 29.998 (s) remaining
[07:02:26.738] connect trace: reading info, version and upgrading to secure if necessary, 29.997 (s) remaining
[07:02:26.739] connect trace: starting reader, 29.996 (s) remaining
[07:02:26.74] connect trace: starting writer, 29.995 (s) remaining
[07:02:26.741] connect trace: sending connect message, 29.995 (s) remaining
[07:02:26.741] connect trace: sending initial ping, 29.994 (s) remaining
[07:02:26.742] connect trace: updating status to connected, 29.993 (s) remaining
[07:02:26.742] connect trace: status updated

[scottf]

That would probably be useful. I'll look into it when I get a chance, you are always welcome to make a fork and submit a PR.

[hoodaajay1]

Sure I would be happy to do that. By the way I tried to check in to a new branch but got 403. Thanks

…

Sent from my iPhone

On Sep 20, 2021, at 10:17 AM, Scott Fauerbach ***@***.***> wrote:  That would probably be useful. I'll look into it when I get a chance, you are always welcome to make a fork and submit a PR. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[scottf]

@hoodaajay1 You probably need to fork and also you will need to sign your commits. https://docs.github.com/en/github/authenticating-to-github/managing-commit-signature-verification/signing-commits

[scottf]

#1106