Ivan Kozlovic

@bloodbare Would you be able to send the configuration file of all server involved and the configuration of the JS consumer you use (if any). I see the subscription output,...

@trading-peter Oh my... yes, it seems that I made a change more than 2 years ago whereby Start() (that calls AcceptLoop) is no longer blocking since the actual accept loop...

Thank you for your interest. Unfortunately, there is no plan to implement QoS2 in NATS Server at this stage.

@robinsmidsrod There is no document per-se. I have written the MQTT code in the NATS Server and I am concerned with the added complexity of QoS2 and that we don't...

Could it be that there is a deadlock in the leafnodes that cause messages to accumulate and not being drained? @vividvilla would it be possible for you to re-run the...

@vividvilla I don't see the stacks attached, which are the ones that will help us see if there is a deadlock happening in the leafnodes, causing the memory buildup in...

@vividvilla The "good" news, is that there is no deadlock, but servers are really busy doing this kind of operations: ``` goroutine 129130 [runnable]: bytes.(*Buffer).WriteString(0xc0024a9140, {0xc001b36690, 0x2f}) /home/travis/.gimme/versions/go1.17.9.linux.amd64/src/bytes/buffer.go:180 +0xfa net/http.Header.writeSubset(0xa0fe80,...

What exactly should we then report? Exporting the whole `tls.Conn.ConnectionState().PeerCertificates` will be way too much content. Also note that this will be empty unless the server requires client certificate. We...

@RedShift1 @philpennock I am struggling to know what we would need to include as the new TLS details entry. I am assuming that we would report a subset of PeerCertificates...

@RedShift1 I saw your original comment, my point is that the "Subject" is actually a pkix.Name (see https://pkg.go.dev/crypto/x509/pkix#Name) and that seem a lot to return. As for the fingerprint, what...