Scott Fauerbach

This is fixed by a bug fix with Poison Pill

@HenriNext I develop on Windows 11 and have no problem running the test suite multiple times daily. I also just double checked my ubuntu machine and no problem there either....

I run on windows with the server in my path. I have also tested using nats_server_path. Here is an interesting discussion about System.getEnv(...) failing, it has to do with the...

Closing not reproducible.

The problem in your java code is that your connection to the hub does not required the `jsDomain` to be set. If you tell the client the domain to use,...

I'm also following up with the developer of the CLI. Maybe the cli made an assumption, or it's possible they did it intentionally considering the common use case or they...

The CLI developer has responded and raised this as an issue in the CLI and go client.

An issue has been opened on the go client. https://github.com/nats-io/nats.go/issues/1648

I think I can reproduce the problem. I'll have to figure out how to fix it now.

Fix is here https://github.com/nats-io/nats.java/pull/1160