Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ConnectionListener shows DISCONNECTED twice #274

Closed
oliverhausler opened this issue Sep 24, 2019 · 4 comments
Closed

ConnectionListener shows DISCONNECTED twice #274

oliverhausler opened this issue Sep 24, 2019 · 4 comments

Comments

@oliverhausler
Copy link

.connectionListener((conn, type) -> log.info(name + ": " + type.name())) logs this:

image

Probably not a big issue, but wanted to let you know.

@sasbury
Copy link
Contributor

sasbury commented Sep 24, 2019

Any chance you could capture a stack trace just so i can track this down. As you say, not a huge deal but maybe an easy fix.

@oliverhausler
Copy link
Author

oliverhausler commented Sep 24, 2019

There is no stacktrace. The exception you see comes from the errorListener not the connectionListener. On the connectionListener I am just seeing the event.

I could get you the stacktrace for the exceptionOccurred event, but I don't think it will help much.

@sasbury
Copy link
Contributor

sasbury commented Sep 24, 2019

sorry, i meant, can you do a (new Exception()).printStackTrace() in that callback so we can see where they happen. I can try it on a sample when I get a chance, just figured you might be able to grab it while you are poking around.

@oliverhausler
Copy link
Author

I don't see much as our k8s environment has just been set up and logging isn't fully configured. Stack traces are not in sequence. Hope it helps.

Only line which I see repeatedly in NATS is this: at io.nats.client.impl.NatsConnection.lambda$processConnectionEvent$10(NatsConnection.java:1420)

image

@sasbury sasbury mentioned this issue Oct 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants