Yasong Li
Yasong Li
Here is the relevant connz information. `out_bytes` and `out_msg` are increasing. 
I noticed this issue https://github.com/nats-io/nats-server/issues/4736. Although I am using mqtt, my consumer behavior is very similar to the description in this comment https://github.com/nats-io/nats-server/issues/4736#issuecomment-1955690764 . It is possible that the two...
> @fly2F I am going to pursue this from the MQTT angle, let @derekcollison comment on whether there may be an underlying JetStream issue. To make sure I understand this...
> @fly2F I am going to pursue this from the MQTT angle, let @derekcollison comment on whether there may be an underlying JetStream issue. To make sure I understand this...
@levb Thank you. I have two single-node NATS servers that experienced problems with MQTT clients not receiving messages within 2 days. These two servers are used for testing. One has...
@levb Thanks! The strange thing is that when the mqtt client connection cannot receive messages, out_msgs and out_bytes in connz are increasing, but the Trace level log is not included...
I have upgraded the version and I cannot reproduce the problem. @levb @derekcollison Thanks!