Scott Fauerbach

@sasbury This doesn't seem right: https://github.com/nats-io/nats.java/blob/main/src/main/java/io/nats/client/impl/NatsConnection.java#L1275 handleCommunicationIssue closes the socket. I can definitely see throwing the IllegalStateException here but closing the socket b/c it was asked to ping and we're...

Closed as resolved in #432

Is this repeatable against a local, non-cluster server? This seems unusual, the subscribe request reply should take milliseconds. not accounting for things like network latency, server load.

I'm very concerned about putting a synchronize block around that code since it does not explain why there is a timeout, even if the problem appears to go away when...

Repo is End Of Life

It's probably contention for locks for the publish queue. I would start working around this by spreading your publishing threads over more actual connections to the server, maybe even using...

The latest release should take care of this, but it depends on exactly your type of consumer. Only durable consumers or ephemeral consumers with a inactive threshold that is longer...

@rlabbe82 Any chance you have some pseudo / code I could use to repeat this? What version of the clients and service are you using? You said it's repeatable across...

Thanks for the input, that's an interesting observation about when the server is in a container.

> @scottf Also seeing this bug in our logs (the broker was restarted by our update utility on an embedded Yocto system) Side note, can we avoid "broker" and use...