Scott Fauerbach

I'm happy to discuss this with the clients development teams, but you can certainly accomplish this yourself, by having your synchronous message handler distribute the messages asynchronously.

> Vertx for nats may help : https://github.com/nats-io/nats-java-vertx-client It won't. That vertx client is a wrapper around the existing client. It's on the roadmap to replace the connection layer in...

What version of the client? What is the connection timeout (default?) What does your network between the client and server look like? What cli commands are you running? Can you...

Can you move to the latest client. 2.15 is pretty old. There could be an issue in there, but I can't remember. Also which line of code is giving a...

@liyancoding Are you still able to reproduce this? Is there a main or something that uses the code you provided, I'm trying to reproduce this.

@liyancoding I have an update on this based on another user report. The other user's code was doing a async publish, and in their error handler that they attached to...

jetstream is really just a functional wrapper around the connection and there is no cost except instantiation and initialization

As far as the issues you have with a timeout there are at least 2 possible causes. 1. The server has disconnected or just too busy (probably not too busy...

> I'm facing the same problem, still looking for solution. Can you give some more details or explanation about your specific problem, you environment, your threading? Code examples that reproduce...

This example works running a cluster directly on my machine. I'm almost 100% sure this is a docker networking issue and is a different issue than the original one reported,...