Ivan Kozlovic

@BlizzTom The `nats.js` uses the `INFO` protocol to get the list of possible "connect URLs", which is a list of URLs that a client can reconnect to (augmented to the...

Another side note: when you say: `But sometimes, when I restart the server, I see it starts to process events that I know were already processed before.`, yes, it is...

Could you show excerpt of logs that show that? If that's the case, don't think this is a problem with the client (unless, like I said, there would have been...

That's not NATS Streaming server log.. what I would want to see is a trace in the server log that shows that the ACK for a given message was received...

I think it is just due to the detection of consumer(s) that are falling behind and the server stalls the fast producers. Running the server in Debug mode (-D) should...

@derekcollison @wjordan Sorry for the delay. I did look at this PR but with PR #5602 test, I still could see duplicate routes with @wjordan approach. The reason this PR...

@nenych We believe that the issue of having messages routed to a server that did not seemingly have the application with a given subscription running has been fixed. You may...

@derekcollison @Karimerto I will, but from my first quick read of the issue, I would think that this is expected. After all, the one that exports the service is the...

@Karimerto I am running the same setup locally and can indeed "reproduce" the behavior, but my understanding is that it works as expected. You have the "HubAccount" exporting the service,...

@levb What I would do to test is modify a test to cause a data race or whatever the matrix is supposed to catch and see if the output is...